start_project_planning · Vibe Stack MCP: Risk & Policy

WHAT IT DOES

What start_project_planning does on Vibe Stack MCP

AI agents invoke start_project_planning to trigger actions in Vibe Stack MCP. 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_project_planning needs a policy

start_project_planning triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_project_planning Rate-limited

start_project_planning 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_project_planning": {
      "limits": [
        {
          "counter": "start_project_planning_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 Vibe Stack MCP, so you can run agents against it safely.

FAQ

Questions about start_project_planning

What does the start_project_planning tool do? +

start_project_planning. It is categorised as a Execute tool in the Vibe Stack MCP 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_project_planning? +

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

What risk level is start_project_planning? +

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

Can I rate-limit start_project_planning? +

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

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

start_project_planning is provided by the Vibe Stack MCP server (memextech/vibe-plan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.