分析使用趋势，对比今日和本月的平均使用情况
AI agents call analyze_usage_trend 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 analyzes existing usage statistics by comparing temporal trends. It performs read-only querying and statistical computation on historical data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could only request unauthorized usage reports, not alter data or trigger external actions.
From the tool's definition Tool name 'analyze_usage_trend' and description indicate data analysis and comparison ('对比今日和本月的平均使用情况' = 'compare today and monthly average usage') with no modification, deletion, or execution capabilities.
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 analyze_usage_trend: 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.
analyze_usage_trend 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 analyze_usage_trend 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 analyze_usage_trend. 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.
analyze_usage_trend 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 →