usage_stats

Return summary stats of how this MCP server has been used (top tools called, success rate, recent activity). Free. Use to verify your own integration is hitting the right tools.

SERVEROmnicall — Agent Tools Gateway SOURCEhttps://omnicall.gocreativeai.com/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/com-gocreativeai-omnicall-agent-tools/usage-stats.md

WHAT IT DOES

What usage_stats does on Omnicall — Agent Tools Gateway

AI agents call usage_stats to retrieve information from Omnicall — Agent Tools Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why usage_stats is rated Low

This is a read-only diagnostic/monitoring tool that retrieves historical usage data about the MCP server itself. It has no side effects, does not execute code, does not modify state, and does not involve financial operations. The purpose is introspection and integration validation.

From the tool's definition Tool returns 'summary stats' and 'usage' information with no modification capability; explicitly described as free and for verification/monitoring purposes. Verbs: 'Return', 'verify'.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs usage_stats safely

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

usage_stats Allowed

usage_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": {
    "usage_stats": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Omnicall — Agent Tools Gateway, apply this rule, and every usage_stats call is checked against it from then on.

FAQ

Questions about usage_stats

What does the usage_stats tool do? +

Return summary stats of how this MCP server has been used (top tools called, success rate, recent activity). Free. Use to verify your own integration is hitting the right tools. It is categorised as a Read tool in the Omnicall — Agent Tools Gateway MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on usage_stats? +

Register the Omnicall — Agent Tools Gateway MCP server in PolicyLayer and add a rule for usage_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 Omnicall — Agent Tools Gateway. Nothing to install.

What risk level is usage_stats? +

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

Can I rate-limit usage_stats? +

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

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

usage_stats is provided by the Omnicall — Agent Tools Gateway MCP server (https://omnicall.gocreativeai.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Omnicall — Agent Tools Gateway, and thousands of servers like it.

This server

All 79 Omnicall — Agent Tools Gateway 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 →