Check your SnapAPI account usage, quota, and plan details for the current billing period.
AI agents call get_usage to retrieve information from SnapAPI 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 account metadata and usage statistics without creating, modifying, deleting, or executing any operations. It is purely informational, making it a Read category tool with low severity since misuse would only expose usage data rather than enable harmful actions.
From the tool's definition Tool name 'get_usage' and description 'Check your SnapAPI account usage, quota, and plan details' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Check your SnapAPI account usage, quota, and plan details for the current billing period. It is categorised as a Read tool in the SnapAPI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SnapAPI MCP Server 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 SnapAPI MCP Server. 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 SnapAPI MCP Server MCP server (sleywill/snapapi-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 →