get_usage

Check your current API usage quota and rate limits for the billing period. Shows per-channel usage (phone, URL, text, email, document) with limits and remaining counts. QR lookups consume URL quota.

Server ScamVerify scamverifyai/scamverify-mcp
Category Read
Risk class Low
Parameters 00 required

What get_usage does on ScamVerify

AI agents call get_usage to retrieve information from ScamVerify without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_usage needs a policy

This is a simple query tool that provides billing and usage statistics without side effects. It does not create, modify, or delete data, nor does it execute external operations or process threats. The worst-case misuse (an agent reading usage stats repeatedly) poses minimal risk. Classified as Read/low severity.

From the tool's definition Tool retrieves API usage quota, rate limits, and consumption metrics ('Check your current API usage quota and rate limits... Shows per-channel usage... with limits and remaining counts').

Questions about get_usage

What does the get_usage tool do? +

Check your current API usage quota and rate limits for the billing period. Shows per-channel usage (phone, URL, text, email, document) with limits and remaining counts. QR lookups consume URL quota. It is categorised as a Read tool in the ScamVerify MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_usage? +

Register the ScamVerify 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 ScamVerify. Nothing to install.

What risk level is get_usage? +

get_usage is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_usage? +

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.

How do I block get_usage completely? +

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.

What MCP server provides get_usage? +

get_usage is provided by the ScamVerify MCP server (scamverifyai/scamverify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.