start_plan · Pathfinder MCP Server MCP: Risk & Policy

WHAT IT DOES

What start_plan does on Pathfinder MCP Server

AI agents invoke start_plan to trigger actions in Pathfinder MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why start_plan needs a policy

This tool executes a workflow state transition rather than simply reading or writing static data. It triggers phase-gated logic and context management operations. However, the blast radius is low because phase transitions in a gated approval workflow are designed to be reversible and non-destructive—this does not delete data, move money, or irreversibly change system state.

From the tool's definition Tool 'start_plan' transitions workflow state from research to plan phase. The description indicates state management and phase transitions that trigger automated processes ('automatic context management' mentioned in server description).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_plan Rate-limited

start_plan stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_plan": {
      "limits": [
        {
          "counter": "start_plan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about start_plan

What does the start_plan tool do? +

Transition from research to plan phase. It is categorised as a Execute tool in the Pathfinder MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_plan? +

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

What risk level is start_plan? +

start_plan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_plan? +

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

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

start_plan is provided by the Pathfinder MCP Server MCP server (jamesctucker/pathfinder-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.