teammate_approve_plan

Approve a submitted plan

SERVERClaude Flow SOURCEclaude-flow

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/teammate-approve-plan.md

WHAT IT DOES

What teammate_approve_plan does on Claude Flow

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.

RISK

Why teammate_approve_plan is rated Medium

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

RECOMMENDED RULE

The rule that runs teammate_approve_plan safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For teammate_approve_plan, this is the rule to start with:

teammate_approve_plan Rate-limited

teammate_approve_plan stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "teammate_approve_plan": {
      "limits": [
        {
          "counter": "teammate_approve_plan_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every teammate_approve_plan call is checked against it from then on.

FAQ

Questions about teammate_approve_plan

What does the teammate_approve_plan tool do? +

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.

How do I enforce a policy on teammate_approve_plan? +

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.

What risk level is teammate_approve_plan? +

teammate_approve_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit teammate_approve_plan? +

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.

How do I block teammate_approve_plan completely? +

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.

What MCP server provides teammate_approve_plan? +

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.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools →

Across the catalogue

team_manager_plan_room on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →