AI agents use gsd_plan_phase to create or update resources in Gsd — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gsd environment.
This tool creates planning artifacts (task plans) for a project phase, which modifies the GSD project state reversibly. It does not execute arbitrary code, delete data, move money, or merely read data. Writing new planning structures into the project lifecycle qualifies as Write category.
From the tool's definition Tool description states 'create task plans for a phase', indicating creation of planning data within the GSD project lifecycle. The verb 'create' combined with 'task plans' confirms data generation and modification.
Attacks that exploit this kind of access
Research and create task plans for a phase. It is categorised as a Write tool in the Gsd MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gsd MCP server in PolicyLayer and add a rule for gsd_plan_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.
gsd_plan_phase is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gsd_plan_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.
Set action: deny in the PolicyLayer policy for gsd_plan_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.
gsd_plan_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →