Return the context tier assignment (Hot/Domain/Cold) for all spec artifacts in the active feature.
AI agents call sdd_context_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.
This tool retrieves and displays metadata about existing specification artifacts (their Hot/Domain/Cold context tier classifications). It performs a pure read operation with no side effects, no code execution, no data modification, and no destructive actions.
From the tool's definition Tool description explicitly states 'Return the context tier assignment' - a retrieval operation that queries and reports the status of spec artifacts without modifying or executing operations.
Documented attack patterns abuse exactly the kind of access sdd_context_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_context_status:
{
"version": "1",
"default": "deny",
"tools": {
"sdd_context_status": {}
}
}sdd_context_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.
Return the context tier assignment (Hot/Domain/Cold) for all spec artifacts in the active feature. 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_context_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_context_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_context_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_context_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_context_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.