get_stats

Get comprehensive session statistics. Shows token savings, duplicate detection counts, entropy distribution, dependency graph stats, checkpoint status, and cost estimates.

ServerEntroly Context Engine
CategoryRead

How to control get_stats ↓

WHAT IT DOES

What get_stats does on Entroly Context Engine

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

THE RISK

Low Risk

Why get_stats needs a policy

This tool retrieves and reports statistical data about the current session state without modifying any data, triggering external actions, or causing side effects. It is purely informational/observational in nature, fitting the Read category with low severity due to lack of blast radius from misuse.

From the tool's definition Tool name 'get_stats' and description 'Get comprehensive session statistics' with retrieval-only operations: 'Shows token savings, duplicate detection counts, entropy distribution, dependency graph stats, checkpoint status, and cost estimates.' No mutations,…

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

POLICY

How to control get_stats

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_stats": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Entroly Context Engine tools

Execute execute_flow Execute a full canonical epistemic flow end-to-end. Routes the query through the Execute start_workspace_listener Start a background workspace listener that continuously feeds repo changes into CogOps. Execute epistemic_route Route a query through the CogOps Epistemic Ingress Controller. Inspects 4 signals Execute process_change Process a code change through the Change-Driven pipeline (Flow ④). Full pipeline: Execute manage_skills Manage the CogOps skill lifecycle (Evolution layer). Actions: - list: Sho Write compile_docs Compile markdown documentation files into belief artifacts. Ingests project-level Write ingest_diagram Ingest an architecture or flow diagram into the context memory. Converts Mermaid, Write ingest_voice Ingest a voice/meeting transcript into the context memory. Converts pre-transcrib

All 52 Entroly Context Engine tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_stats

What does the get_stats tool do? +

Get comprehensive session statistics. Shows token savings, duplicate detection counts, entropy distribution, dependency graph stats, checkpoint status, and cost estimates. It is categorised as a Read tool in the Entroly Context Engine MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_stats? +

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

What risk level is get_stats? +

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

Can I rate-limit get_stats? +

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

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

get_stats is provided by the Entroly Context Engine MCP server (juyterman1000/entroly). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Entroly Context Engine tool call.

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

CHECK YOUR STACK →

Free to start. No card required.

52 Entroly Context Engine tools catalogued and risk-classified — across an index of 43,000+ MCP servers.