Medium Risk

devplan_generate_plan

Generate a DEVELOPMENT_PLAN.md scaffold. IMPORTANT: This outputs a SCAFFOLD, not a finished plan. REQUIRED WORKFLOW (you MUST follow this): 1. Call this tool to get the scaffold, optionally specifying target (claude, cursor, aider, cline, windsurf, generic) 2. ENHANCE the scaffold by: - Reading t...

Risk signalsAccepts raw HTML/template content (template) · Bulk/mass operation — affects multiple targets

Part of the DevPlan MCP Server server.

devplan_generate_plan can modify DevPlan MCP Server data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE DEVPLAN MCP SERVER →

Free to start. No card required.

AI agents use devplan_generate_plan to create or modify resources in DevPlan MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call devplan_generate_plan repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach DevPlan MCP Server.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "devplan_generate_plan": {
      "limits": [
        {
          "counter": "devplan_generate_plan_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full DevPlan MCP Server policy for all 25 tools.

Get this rule live on your own DevPlan MCP Server server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DEVPLAN MCP SERVER →

View all 25 tools →

These attack patterns abuse exactly the kind of access devplan_generate_plan gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so devplan_generate_plan only ever does what you allow.

SECURE DEVPLAN MCP SERVER →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the devplan_generate_plan tool do? +

Generate a DEVELOPMENT_PLAN.md scaffold. IMPORTANT: This outputs a SCAFFOLD, not a finished plan. REQUIRED WORKFLOW (you MUST follow this): 1. Call this tool to get the scaffold, optionally specifying target (claude, cursor, aider, cline, windsurf, generic) 2. ENHANCE the scaffold by: - Reading the project's existing codebase - Writing COMPLETE file contents for each subtask (no "Add to" instructions) - Including ALL imports in every code block - Making test fixtures self-contained in each test file - Providing exact line context for any file modifications 3. Call devplan_validate_haiku_executable to verify the plan 4. If validation fails, fix the issues and re-validate 5. ONLY present the plan to the user after validation passes The user should NEVER see the raw scaffold - only the enhanced, validated plan.. It is categorised as a Write tool in the DevPlan 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 devplan_generate_plan? +

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

What risk level is devplan_generate_plan? +

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

Can I rate-limit devplan_generate_plan? +

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

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

devplan_generate_plan is provided by the DevPlan MCP Server MCP server (https://devplan-mcp-server.mike-c63.workers.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every DevPlan MCP Server tool call.

Deterministic rules across all 25 DevPlan MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.