Low Risk

sc_guidance

Get detailed behavioral instructions for the current state (e.g., Ambiguity Resolution Loop steps).

Part of the Mcp Spec Cli server.

sc_guidance is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE MCP SPEC CLI →

Free to start. No card required.

AI agents call sc_guidance to retrieve information from Mcp Spec Cli without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though sc_guidance only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "sc_guidance": {}
  }
}

See the full Mcp Spec Cli policy for all 16 tools.

Get this rule live on your own Mcp Spec Cli server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MCP SPEC CLI →

View all 16 tools →

These attack patterns abuse exactly the kind of access sc_guidance gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so sc_guidance only ever does what you allow.

SECURE MCP SPEC CLI →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the sc_guidance tool do? +

Get detailed behavioral instructions for the current state (e.g., Ambiguity Resolution Loop steps).. It is categorised as a Read tool in the Mcp Spec Cli MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sc_guidance? +

Register the Mcp Spec Cli MCP server in PolicyLayer and add a rule for sc_guidance: 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 Mcp Spec Cli. Nothing to install.

What risk level is sc_guidance? +

sc_guidance is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sc_guidance? +

Yes. Add a rate_limit block to the sc_guidance 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.

How do I block sc_guidance completely? +

Set action: deny in the PolicyLayer policy for sc_guidance. 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.

What MCP server provides sc_guidance? +

sc_guidance is provided by the Mcp Spec Cli MCP server (mcp-spec-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Spec Cli tool call.

Deterministic rules across all 16 Mcp Spec Cli tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.