Approve a submitted plan
AI agents use teammate_approve_plan 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 creates or modifies data reversibly by transitioning a plan's approval state. It is Write category (not Read, as it has side effects; not Execute/Destructive, as approval is not irreversible and does not run arbitrary code; not Financial, as no money moves).
From the tool's definition Tool name 'teammate_approve_plan' and description 'Approve a submitted plan' indicate a state-change operation that modifies the status of a plan from pending/submitted to approved.
Attacks that exploit this kind of access
Approve a submitted plan. 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_approve_plan: 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_approve_plan 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_approve_plan 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_approve_plan. 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_approve_plan 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.