Low Risk

ctx_stats

Returns context consumption statistics for the current session. Shows total bytes returned to context, breakdown by tool, call counts, estimated token usage, and context savings ratio.

How to control ctx_stats ↓

What ctx_stats does on Context Mode

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

Low Risk

Why ctx_stats needs a policy

ctx_stats is a pure read operation that queries and reports session metrics. It retrieves information about context usage without creating, modifying, or deleting any data. The tool provides telemetry and statistics only, making it a straightforward Read category classification with low severity risk.

From the tool's definition Tool returns statistics and metrics ('context consumption statistics', 'total bytes returned', 'breakdown by tool', 'call counts', 'estimated token usage', 'context savings ratio').

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

How to control ctx_stats

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

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

ctx_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 Context Mode — 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.

Related tools and policies

Go deeper

Questions about ctx_stats

What does the ctx_stats tool do? +

Returns context consumption statistics for the current session. Shows total bytes returned to context, breakdown by tool, call counts, estimated token usage, and context savings ratio. It is categorised as a Read tool in the Context Mode MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ctx_stats? +

Register the Context Mode MCP server in PolicyLayer and add a rule for ctx_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 Context Mode. Nothing to install.

What risk level is ctx_stats? +

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

Can I rate-limit ctx_stats? +

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

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

ctx_stats is provided by the Context Mode MCP server (mksglu/context-mode). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Context Mode tool call.

Start from Context Mode, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

11 Context Mode tools catalogued and risk-classified — across an index of 43,000+ 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.