This record as markdown: /tools/allmcp/get-usage.md
What get_usage does on Allmcp
AI agents call get_usage to retrieve information from Allmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_usage is rated Low
Based on the naming convention, 'get_usage' appears to be a read operation that retrieves usage data without modifying state. The empty description lowers confidence slightly, but the 'get_' prefix strongly suggests a query/retrieval operation. No capability to modify, delete, execute external operations, or commit financial transactions is evident.
From the tool's definition Tool name 'get_usage' indicates retrieval of usage metrics or statistics. No destructive operations or side effects are implied by the name.
Attacks that exploit this kind of access
The rule that runs get_usage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Allmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_usage, this is the rule to start with:
get_usage 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 Allmcp, apply this rule, and every get_usage call is checked against it from then on.
Questions about get_usage
get_usage is a read tool on the All MCP server. It is categorised as a Read tool in the Allmcp MCP Server, which means it retrieves data without modifying state.
Register the All MCP server in PolicyLayer and add a rule for get_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 Allmcp. Nothing to install.
get_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 get_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 get_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.
get_usage is provided by the All MCP server (Perception-Dynamics-Inc/allmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on All, and thousands of servers like it.
This server
Across the catalogue