获取当前API速率限制使用情况统计
AI agents call get_rate_limit_stats to retrieve information from Get笔记 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves rate limit statistics from the GetBiji API. It performs read-only monitoring operations with no ability to modify data, execute commands, or trigger external effects. The blast radius is minimal—misuse would only expose usage metrics to the AI agent, not compromise data or functionality.
From the tool's definition Tool name 'get_rate_limit_stats' and description '获取当前API速率限制使用情况统计' (Get current API rate limit usage statistics) indicates retrieval of monitoring/usage data without modification or side effects.
Attacks that exploit this kind of access
获取当前API速率限制使用情况统计. It is categorised as a Read tool in the Get笔记 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Get笔记 MCP Server MCP server in PolicyLayer and add a rule for get_rate_limit_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 Get笔记 MCP Server. Nothing to install.
get_rate_limit_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 get_rate_limit_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 get_rate_limit_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.
get_rate_limit_stats is provided by the Get笔记 MCP Server MCP server (pancrepal-xiaoyibao/get_biji_mcp). 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 →