teammate_submit_plan · Ruflo MCP: Risk & Policy

WHAT IT DOES

What teammate_submit_plan does on Ruflo

AI agents use teammate_submit_plan to create or update resources in Ruflo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ruflo environment.

WHY IT NEEDS A POLICY

Why teammate_submit_plan needs a policy

This tool creates or modifies plan data (write operation) rather than merely reading it. In a multi-agent swarm system, submitting a plan could trigger downstream autonomous actions by other agents, but the tool itself is submission/creation, not execution of the plan.

From the tool's definition Tool name 'submit_plan' indicates creation/modification of a plan artifact. Description states 'Submit a plan for team approval', which implies persisting a plan object that other agents or systems will review and act upon.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

teammate_submit_plan Rate-limited

teammate_submit_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_submit_plan": {
      "limits": [
        {
          "counter": "teammate_submit_plan_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ruflo, so you can run agents against it safely.

FAQ

Questions about teammate_submit_plan

What does the teammate_submit_plan tool do? +

Submit a plan for team approval. It is categorised as a Write tool in the Ruflo 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_submit_plan? +

Register the Ruflo MCP server in PolicyLayer and add a rule for teammate_submit_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 Ruflo. Nothing to install.

What risk level is teammate_submit_plan? +

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

Can I rate-limit teammate_submit_plan? +

Yes. Add a rate_limit block to the teammate_submit_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_submit_plan completely? +

Set action: deny in the PolicyLayer policy for teammate_submit_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_submit_plan? +

teammate_submit_plan is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.