audit_stats

Summary of recent activity: call counts, failures, busiest tools, per-profile split.

SERVERMcp Hands SOURCEhuocai250/mcp-hands

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-hands/audit-stats.md

WHAT IT DOES

What audit_stats does on Mcp Hands

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

RISK

Why audit_stats is rated Low

Even though audit_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 audit_stats safely

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

audit_stats Allowed

audit_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": {
    "audit_stats": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Hands, apply this rule, and every audit_stats call is checked against it from then on.

FAQ

Questions about audit_stats

What does the audit_stats tool do? +

Summary of recent activity: call counts, failures, busiest tools, per-profile split. It is categorised as a Read tool in the Mcp Hands MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on audit_stats? +

Register the Mcp Hands MCP server in PolicyLayer and add a rule for audit_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 Mcp Hands. Nothing to install.

What risk level is audit_stats? +

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

Can I rate-limit audit_stats? +

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

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

audit_stats is provided by the Mcp Hands MCP server (huocai250/mcp-hands). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Hands, and thousands of servers like it.

This server

All 378 Mcp Hands 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 →