AI agents call sdd_history to retrieve information from Forgespec without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical information about project phase transitions without modifying data, executing operations, or triggering external actions. It is a straightforward query operation that reads existing records. The low severity reflects minimal risk if accessed by an AI agent, as it only exposes historical audit information.
From the tool's definition Tool name and description indicate it 'Get[s] the SDD phase history' and 'Shows all contract transitions in chronological order' — pure data retrieval with no modifications or side effects.
Attacks that exploit this kind of access
Get the SDD phase history for a project. Shows all contract transitions in chronological order. It is categorised as a Read tool in the Forgespec MCP Server, which means it retrieves data without modifying state.
Register the Forgespec MCP server in PolicyLayer and add a rule for sdd_history: 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 Forgespec. Nothing to install.
sdd_history 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 sdd_history 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 sdd_history. 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.
sdd_history is provided by the Forgespec MCP server (lleontor705/forgespec-mcp). 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 →