AI agents call gsd_progress to retrieve information from Gsd without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only shows/displays information about the next step in the lifecycle. It is a read-only query with no side effects. Severity is low as misuse would at most expose project state information.
From the tool's definition 'Show what step to run next in the GSD lifecycle' — purely displays/retrieves the next step, no modification implied
Attacks that exploit this kind of access
Show what step to run next in the GSD lifecycle. It is categorised as a Read tool in the Gsd MCP Server, which means it retrieves data without modifying state.
Register the Gsd MCP server in PolicyLayer and add a rule for gsd_progress: 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_progress is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gsd_progress 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_progress. 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_progress 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.
gsd_progress is one line of Gsd's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →