Check current API usage and limits. Returns monthly quota information including usage count and remaining requests.
AI agents call check_usage to retrieve information from Noun Project MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and reports usage statistics and quota information. It performs a read-only operation that queries the current state of the user's API account without modifying, deleting, executing code, or triggering external operations. The blast radius of misuse is minimal—worst case an agent repeatedly calls it to consume rate limit quota, but no destructive or unintended state changes are possible.
From the tool's definition Tool description states it 'Check[s] current API usage and limits' and 'Returns monthly quota information including usage count and remaining requests.' These are query/retrieval operations with no data modification, deletion, or side effects.
Attacks that exploit this kind of access
Check current API usage and limits. Returns monthly quota information including usage count and remaining requests. It is categorised as a Read tool in the Noun Project MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Noun Project MCP Server MCP server in PolicyLayer and add a rule for check_usage: 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 Noun Project MCP Server. Nothing to install.
check_usage 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 check_usage 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 check_usage. 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.
check_usage is provided by the Noun Project MCP Server MCP server (sgup/noun-project-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
check_usage is one line of Noun Project MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →