AI agents call get_spec to retrieve information from Spec Kit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries specification data without side effects. It matches the Read category pattern of getting/fetching data. The sibling tools (create_spec, export_to_prompt, validate_spec) are more powerful, but this tool itself only retrieves existing specification details.
From the tool's definition Tool name 'get_spec' and description 'Get specification details' indicate data retrieval with no modification capability.
Attacks that exploit this kind of access
Get specification details. It is categorised as a Read tool in the Spec Kit MCP Server, which means it retrieves data without modifying state.
Register the Spec Kit MCP server in PolicyLayer and add a rule for get_spec: 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 Spec Kit. Nothing to install.
get_spec 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 get_spec 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 get_spec. 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.
get_spec is provided by the Spec Kit MCP server (@fast-kit/spec-kit). 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 →