Share message transcript with another teammate
AI agents use teammate_share_transcript to create or update resources in Claude Flow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Flow environment.
This tool sends/shares data (a message transcript) with another user or agent, which constitutes a write/communication action. It creates or transmits a new artifact (the shared transcript) to a recipient. The severity is medium because misuse could expose sensitive conversation data to unintended recipients, but it does not execute code or irreversibly destroy data.
From the tool's definition Share message transcript with another teammate
Attacks that exploit this kind of access
Share message transcript with another teammate. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Flow MCP server in PolicyLayer and add a rule for teammate_share_transcript: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Claude Flow. Nothing to install.
teammate_share_transcript is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the teammate_share_transcript rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for teammate_share_transcript. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
teammate_share_transcript is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.