cli_registry_stats

Get stats about the CLI-Anything registry: total count, categories breakdown.

SERVERMcp Anything SOURCEZaymadkid/mcp-anything

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-anything/cli-registry-stats.md

WHAT IT DOES

What cli_registry_stats does on Mcp Anything

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

RISK

Why cli_registry_stats is rated Low

This tool retrieves aggregate statistics and metadata from a registry. It performs a query operation that does not modify, execute, delete, or move data. The output is informational only, making it a straightforward Read category tool with low severity.

From the tool's definition Tool description states 'Get stats about the CLI-Anything registry: total count, categories breakdown.' The verb 'Get' and the nature of the operation (retrieving statistical information) indicate a read-only query with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cli_registry_stats safely

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

cli_registry_stats Allowed

cli_registry_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": {
    "cli_registry_stats": {}
  }
}

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

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

FAQ

Questions about cli_registry_stats

What does the cli_registry_stats tool do? +

Get stats about the CLI-Anything registry: total count, categories breakdown. It is categorised as a Read tool in the Mcp Anything MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cli_registry_stats? +

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

What risk level is cli_registry_stats? +

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

Can I rate-limit cli_registry_stats? +

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

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

cli_registry_stats is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

All 261 Mcp Anything tools →

Across the catalogue

The MCP Attack Database →

Guides

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