AI agents call validate_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.
Validation typically reads a specification and checks it for correctness, producing a report or result. It does not create, modify, delete, or execute anything. No side effects are implied.
From the tool's definition 'Validate a specification' — validation is a read/analysis operation that checks data against rules without modifying it
Attacks that exploit this kind of access
Validate a specification. 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 validate_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.
validate_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 validate_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 validate_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.
validate_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 →