Low Risk

update_stats

Get current statistics on tasks and active sessions

How to control update_stats ↓

AI agents call update_stats to retrieve information from SystemPrompt Coding Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The tool retrieves statistical information about tasks and sessions. Despite the 'update' in its name, the description clearly states it only 'gets' current statistics, making it a read-only operation with no side effects.

From the tool's definition "Get current statistics on tasks and active sessions"

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

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 update_stats:

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

update_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

Free to start. No card required.

Go deeper

What does the update_stats tool do? +

Get current statistics on tasks and active sessions. It is categorised as a Read tool in the SystemPrompt Coding Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on update_stats? +

Register the SystemPrompt Coding Agent MCP server in PolicyLayer and add a rule for update_stats: 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 update_stats? +

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

Can I rate-limit update_stats? +

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

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

update_stats 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.

Free to start. No card required.

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.