This record as markdown: /tools/7836246-claude-team-mcp/usage-stats.md
What usage_stats does on Claude Team MCP
AI agents call usage_stats to retrieve information from Claude Team MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why usage_stats is rated Low
This tool retrieves and displays historical usage metrics about model performance. It does not create, modify, delete, or execute any operations—it only queries and presents data. Therefore it is classified as Read with low severity, as misuse would only expose informational data about model usage patterns without causing any operational harm.
From the tool's definition Tool name 'usage_stats' and description state it 'views usage statistics' (调查各模型的使用统计) including call counts, success rates, and average latency. These are query/retrieval operations with no side effects.
Attacks that exploit this kind of access
The rule that runs usage_stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Team MCP, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Team MCP, apply this rule, and every usage_stats call is checked against it from then on.
Questions about usage_stats
查看各模型的使用统计(调用次数、成功率、平均耗时). It is categorised as a Read tool in the Claude Team MCP MCP Server, which means it retrieves data without modifying state.
Register the Claude Team 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 Claude Team MCP. Nothing to install.
usage_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
usage_stats is provided by the Claude Team MCP server (7836246/claude-team-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Team, and thousands of servers like it.
This server
Across the catalogue