brain_stats

Ledger stats: total events, spans, latest-event timestamp.

SERVER2ndm1nd Runtime SOURCEbayraak/2ndm1nd-runtime

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/2ndm1nd-runtime/brain-stats.md

WHAT IT DOES

What brain_stats does on 2ndm1nd Runtime

AI agents call brain_stats to retrieve information from 2ndm1nd Runtime without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why brain_stats is rated Low

Even though brain_stats only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs brain_stats safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 2ndm1nd Runtime, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For brain_stats, this is the rule to start with:

brain_stats Allowed

brain_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 2ndm1nd Runtime, apply this rule, and every brain_stats call is checked against it from then on.

FAQ

Questions about brain_stats

What does the brain_stats tool do? +

Ledger stats: total events, spans, latest-event timestamp. It is categorised as a Read tool in the 2ndm1nd Runtime MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on brain_stats? +

Register the 2ndm1nd Runtime MCP server in PolicyLayer and add a rule for brain_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 2ndm1nd Runtime. Nothing to install.

What risk level is brain_stats? +

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

Can I rate-limit brain_stats? +

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

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

brain_stats is provided by the 2ndm1nd Runtime MCP server (bayraak/2ndm1nd-runtime). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 2ndm1nd Runtime, and thousands of servers like it.

This server

All 5 2ndm1nd Runtime tools →

Across the catalogue

cache_stats on ACE-MCP → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →