Load essential spec workflow instructions to guide feature development from idea to implementation. # Instructions Call this tool FIRST when users request spec creation, feature development, or mention specifications. This provides the complete workflow sequence (Requirements → Design → Tasks → ...
Part of the Spec Workflow MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call spec-workflow-guide to perform operations in Spec Workflow. While the risk category is not fully classified, applying a rate limit gives you visibility into how often the tool is called and prevents unexpected bursts of activity from autonomous agents.
Applying a policy to spec-workflow-guide gives you an audit trail of every call an AI agent makes. Even for low-risk tools, visibility into agent behaviour helps you debug issues, optimise workflows, and maintain compliance with your organisation's security requirements.
Apply a rate limit to control usage and monitor for unexpected behaviour.
tools:
spec-workflow-guide:
rules:
- action: allow
rate_limit:
max: 60
window: 60See the full Spec Workflow policy for all 5 tools.
Agents calling other-class tools like spec-workflow-guide have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Other risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Load essential spec workflow instructions to guide feature development from idea to implementation. # Instructions Call this tool FIRST when users request spec creation, feature development, or mention specifications. This provides the complete workflow sequence (Requirements → Design → Tasks → Implementation) that must be followed. Always load before any other spec tools to ensure proper workflow understanding. Its important that you follow this workflow exactly to avoid errors.. It is categorised as a Other tool in the Spec Workflow MCP Server, which means it performs auxiliary operations.
Add a rule in your Intercept YAML policy under the tools section for spec-workflow-guide. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Spec Workflow MCP server.
spec-workflow-guide is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the spec-workflow-guide rule in your Intercept 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 Intercept policy for spec-workflow-guide. 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.
spec-workflow-guide is provided by the Spec Workflow MCP server (@pimzino/spec-workflow-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept