Returns the current pipeline status including: current phase, completed phases, files on disk, completion percentage, and recommended next action.
AI agents call sdd_get_status to retrieve information from Specky without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
sdd_get_status is a status/monitoring tool that retrieves and reports the current state of a specification development pipeline. It performs no modifications, deletions, executions, or financial operations. The blast radius of misuse is minimal - an agent cannot cause harm by querying status information. This is a canonical Read operation.
From the tool's definition Tool returns current pipeline status, completed phases, files on disk, and completion percentage - pure information retrieval with no side effects. Verbs indicate query operation: 'Returns', describing status data.
Documented attack patterns abuse exactly the kind of access sdd_get_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Specky, and nothing reaches the server without passing your rules. This is the rule we recommend for sdd_get_status:
{
"version": "1",
"default": "deny",
"tools": {
"sdd_get_status": {}
}
}sdd_get_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns the current pipeline status including: current phase, completed phases, files on disk, completion percentage, and recommended next action. It is categorised as a Read tool in the Specky MCP Server, which means it retrieves data without modifying state.
Register the Specky MCP server in PolicyLayer and add a rule for sdd_get_status: 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 Specky. Nothing to install.
sdd_get_status 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_get_status 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_get_status. 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_get_status is provided by the Specky MCP server (paulasilvatech/specky). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Specky, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
56 Specky tools catalogued and risk-classified — across an index of 43,000+ MCP servers.