查询特定用户的统计数据，可以指定查询今日或本月
AI agents call query_user_stats to retrieve information from Claude Stats MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and presents existing usage statistics without creating, modifying, deleting, or executing any operations. It is a pure read operation querying a data store. The low severity reflects minimal blast radius: an AI agent misusing this tool could only access usage statistics, with no side effects or ability to alter system state.
From the tool's definition Tool name 'query_user_stats' and description indicate it 'queries statistical data for a specific user' with options to specify 'today or this month' — a retrieval operation with no modification, deletion, or execution of code/commands.
Attacks that exploit this kind of access
查询特定用户的统计数据，可以指定查询今日或本月. It is categorised as a Read tool in the Claude Stats MCP MCP Server, which means it retrieves data without modifying state.
Register the Claude Stats MCP server in PolicyLayer and add a rule for query_user_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 Stats MCP. Nothing to install.
query_user_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 query_user_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 query_user_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.
query_user_stats is provided by the Claude Stats MCP server (upjiang/ai-mcp-study). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →