temporalio / temporalio/features
[Feature Request] Omit HostedMCPTool headers from serialized activity input?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
Some information stored in a payload is more sensitive than the rest of the payload, to the point that it would be ideal to separately secure that information.
Describe the solution you'd like
The sensitive information would not be visible in the temporal UI.
Original Request from user for a specific piece of information
While using HostedMCPTool inside a Temporal workflow we noticed that the tool config (including HTTP headers) is serialized into the activity input/history, so secrets end up in worker logs and the Temporal UI. Is there—or could there be—a way for the plugin to avoid persisting these headers (e.g., a hook to resolve headers only when the activity executes, or built-in redaction)?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by locating HostedMCPTool's serialization path and how activity input reaches history, worker logs, and the Temporal UI; define done as keeping HTTP headers out of persisted activity input while preserving the required execution behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100