16 tools from the Mcp Spec Cli MCP Server, categorised by risk level.
View the Mcp Spec Cli policy →sc_analyze Perform a dedicated ambiguity analysis and self-critique of the drafted document. This step is mandatory before seeking user approval. sc_feedback Provide user feedback or answers to open questions. This clears the associated open questions from the epoch context. sc_guidance Get detailed behavioral instructions for the current state (e.g., Ambiguity Resolution Loop steps). sc_help Learn how to use the CLI tools and get deep documentation. sc_init Initialize a new feature specification. MUST be called from the workspace root directory. Do not cd into subdirectories first. sc_mode Toggle project mode between one-shot and step-through. sc_refresh Force a refresh and synchronization of the internal workflow state machine after editing a document. Use this to verify action persistence. sc_status Get a health check of the active project and discover next steps. sc_todo_list List all implementation tasks and their status. sc_verify A dedicated tool to validate that the last action worked. sc_approve Explicitly approve the current drafted phase after review. 2/5 sc_archive Manually move the project to the completed directory. 2/5 sc_epoch Update the task-epoch context (focus, intentions, hypotheses, questions). 2/5 sc_plan Progress the workflow state (e.g., Requirements -> Design). Automatically archives when finished. 2/5 sc_todo_complete Mark a task as completed. 2/5 The Mcp Spec Cli MCP server exposes 16 tools across 3 categories: Read, Write, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Mcp Spec Cli server.
Mcp Spec Cli tools are categorised as Read (10), Write (5), Execute (1). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept