submit_plan · Agent Communication MCP Server MCP

WHAT IT DOES

What submit_plan does on Agent Communication MCP Server

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

WHY IT NEEDS A POLICY

Why submit_plan needs a policy

submit_plan creates files to store implementation plan content, making it a Write operation. It is not Read (no data retrieval), not Execute (no command/code execution), not Destructive (files can be removed), not Financial. Severity is medium because file creation could consume resources or overwrite existing plans if not validated, but the impact is limited to plan documents in a coordination system.

From the tool's definition Tool description states 'handles file creation internally', indicating the tool creates or modifies data (files). The action is reversible—created files can be deleted or modified later.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_plan Rate-limited

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": {
    "submit_plan": {
      "limits": [
        {
          "counter": "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 Agent Communication MCP Server, so you can run agents against it safely.

FAQ

Questions about submit_plan

What does the submit_plan tool do? +

Submit implementation plan content - handles file creation internally. It is categorised as a Write tool in the Agent Communication MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on submit_plan? +

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

What risk level is submit_plan? +

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

Can I rate-limit submit_plan? +

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

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

submit_plan is provided by the Agent Communication MCP Server MCP server (jerfowler/agent-comm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.