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 → Imp...
AI agents call spec-workflow-guide to retrieve information from Spec Workflow MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and returns workflow instructions/guidance to the AI agent. It does not create, modify, delete, or execute anything; it simply loads procedural documentation to inform subsequent actions. The severity is low because misuse would at worst result in incorrect workflow guidance being loaded, with no direct impact on data or systems.
From the tool's definition 'Load essential spec workflow instructions' and 'provides the complete workflow sequence' — retrieves instructional/guidance content with no side effects
Documented attack patterns abuse exactly the kind of access spec-workflow-guide gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Spec Workflow MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for spec-workflow-guide:
{
"version": "1",
"default": "deny",
"tools": {
"spec-workflow-guide": {}
}
}spec-workflow-guide 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.
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 Read tool in the Spec Workflow MCP MCP Server, which means it retrieves data without modifying state.
Register the Spec Workflow MCP server in PolicyLayer and add a rule for spec-workflow-guide: 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 Workflow MCP. Nothing to install.
spec-workflow-guide 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 spec-workflow-guide 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 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). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Spec Workflow MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 Spec Workflow MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.