gsd_execute_phase · Gsd MCP: Risk & Policy

WHAT IT DOES

What gsd_execute_phase does on Gsd

AI agents invoke gsd_execute_phase to trigger actions in Gsd. 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 gsd_execute_phase needs a policy

This tool executes phase plans, which are operations whose side effects depend on the arguments (the phase and its associated plans). It is not a simple read (no query/retrieve), not a reversible write, and not destructive in nature, but it does trigger external execution of workflows. The 'parallel waves' language suggests orchestration of multiple concurrent operations, making this Execute rather than Write.

From the tool's definition Tool name 'gsd_execute_phase' combined with description 'Execute all plans for a phase in parallel waves' indicates the tool runs/triggers external operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gsd_execute_phase Rate-limited

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

FAQ

Questions about gsd_execute_phase

What does the gsd_execute_phase tool do? +

Execute all plans for a phase in parallel waves. It is categorised as a Execute tool in the Gsd MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on gsd_execute_phase? +

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

What risk level is gsd_execute_phase? +

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

Can I rate-limit gsd_execute_phase? +

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

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

gsd_execute_phase is provided by the Gsd MCP server (m0-ar/gsd-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.