create_change_plan · Mcp Flow MCP: Risk & Policy

WHAT IT DOES

What create_change_plan does on Mcp Flow

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

WHY IT NEEDS A POLICY

Why create_change_plan needs a policy

This tool creates new data (a change plan) but does not execute code, delete files, or move money. It is reversible—a plan can be discarded or replaced. The blast radius is moderate: a malformed plan could misdirect subsequent patch/apply operations, but the plan itself is not destructive until applied by downstream tools (apply_patch).

From the tool's definition Tool name 'create_change_plan' and description 'Assemble a structured change plan' indicates creation of a plan artifact (structured data). In context of a development workflow, this creates/modifies project metadata or internal state representation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_change_plan Rate-limited

create_change_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": {
    "create_change_plan": {
      "limits": [
        {
          "counter": "create_change_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 Mcp Flow, so you can run agents against it safely.

FAQ

Questions about create_change_plan

What does the create_change_plan tool do? +

Assemble a structured change plan from deterministic project context. It is categorised as a Write tool in the Mcp 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 create_change_plan? +

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

What risk level is create_change_plan? +

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

Can I rate-limit create_change_plan? +

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

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

create_change_plan is provided by the Mcp Flow MCP server (remimenguy/mcp-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.