execute_plan · Qontinui MCP Server MCP: Risk & Policy

WHAT IT DOES

What execute_plan does on Qontinui MCP Server

AI agents invoke execute_plan to trigger actions in Qontinui 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 execute_plan needs a policy

This tool executes external operations (visual automation workflows) whose effects depend on the plan content provided as arguments. It triggers automated actions across displays and prior phase outputs, making it an Execute category tool.

From the tool's definition Tool description states it will "Execute a structured implementation plan with sequential AI phases" and context indicates the server "execute[s] visual automation workflows". The tool runs code/automation across multiple phases in separate AI sessions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_plan Rate-limited

execute_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": {
    "execute_plan": {
      "limits": [
        {
          "counter": "execute_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 Qontinui MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_plan

What does the execute_plan tool do? +

Execute a structured implementation plan with sequential AI phases. Each phase runs as a separate AI session with full context from prior phases. It is categorised as a Execute tool in the Qontinui 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 execute_plan? +

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

What risk level is execute_plan? +

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

Can I rate-limit execute_plan? +

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

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

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