check_status

THE RISK

High Risk

Although described as a status check, the tool works by initiating test sessions with external CLI tools (Claude Code SDK and Gemini CLI). This is not a simple read/query of existing state — it actively triggers external operations. The blast radius is medium since misuse could spawn unwanted sessions or consume resources, but it does not directly modify data or execute arbitrary code.

From the tool's definition 'attempting to initiate test sessions' — the tool actively initiates sessions with Claude Code SDK and Gemini CLI, triggering external operations beyond a passive read

Documented attack patterns abuse exactly the kind of access check_status gives an agent:

HOW TO CONTROL CHECK_STATUS

PolicyLayer is an MCP gateway — it sits between your AI agents and SystemPrompt Coding Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for check_status:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_status": {
      "limits": [
        {
          "counter": "check_status_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

check_status stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register SystemPrompt Coding Agent — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More SystemPrompt Coding Agent tools

Destructive clean_state Clean up system state by removing all tasks Destructive end_task End a task and clean up the AI model session Execute create_task Create a new task and start it immediately with Claude Code Execute update_task Send instructions to an active AI process (Claude Code or Gemini CLI) Read get_prompt Get a specific prompt by ID or list all available prompts if no ID is provided Read report Generate a report on task status. Shows all tasks if no ID provided, or details for a spec Read update_stats Get current statistics on tasks and active sessions

All 8 SystemPrompt Coding Agent tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in SystemPrompt Coding Agent → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the check_status tool do? +

Check the status of Claude Code SDK and Gemini CLI availability by attempting to initiate test sessions. It is categorised as a Execute tool in the SystemPrompt Coding Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on check_status? +

Register the SystemPrompt Coding Agent MCP server in PolicyLayer and add a rule for check_status: 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 SystemPrompt Coding Agent. Nothing to install.

What risk level is check_status? +

check_status is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit check_status? +

Yes. Add a rate_limit block to the check_status 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 check_status completely? +

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

check_status is provided by the SystemPrompt Coding Agent MCP server (systempromptio/systemprompt-code-orchestrator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SystemPrompt Coding Agent tool call.

Deterministic rules across all 8 SystemPrompt Coding Agent tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN SYSTEMPROMPT CODING AGENT →

Free to start. No card required.

8 SystemPrompt Coding Agent tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT CHECK_STATUS ON SYSTEMPROMPT CODING AGENT DOES

// THE RISK

// HOW TO CONTROL CHECK_STATUS

// EXPLORE