classic_planner · PlanningCopilot MCP: Risk & Policy

WHAT IT DOES

What classic_planner does on PlanningCopilot

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

WHY IT NEEDS A POLICY

Why classic_planner needs a policy

An AI agent can call classic_planner faster than any human can review — one bad instruction and it creates or modifies resources in PlanningCopilot by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

classic_planner Rate-limited

classic_planner 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": {
    "classic_planner": {
      "limits": [
        {
          "counter": "classic_planner_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 PlanningCopilot, so you can run agents against it safely.

FAQ

Questions about classic_planner

What does the classic_planner tool do? +

classic_planner. It is categorised as a Write tool in the PlanningCopilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on classic_planner? +

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

What risk level is classic_planner? +

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

Can I rate-limit classic_planner? +

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

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

classic_planner is provided by the PlanningCopilot MCP server (spl-bgu/planningcopilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.