Low Risk

get_usage_summary

Summary of recent workspace usage (calls, providers, cost) for the current billing period.

How to control get_usage_summary ↓

What get_usage_summary does on APIClaw

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

Low Risk

Why get_usage_summary needs a policy

This tool retrieves and queries usage statistics and cost data for the current billing period. It has no side effects—it does not create, modify, delete, or execute operations. While it accesses billing/cost information, it is purely informational and read-only.

From the tool's definition Tool name 'get_usage_summary' and description 'Summary of recent workspace usage (calls, providers, cost) for the current billing period' indicate retrieval of usage metrics and billing information without modification.

Documented attack patterns abuse exactly the kind of access get_usage_summary gives an agent:

How to control get_usage_summary

PolicyLayer is an MCP gateway — it sits between your AI agents and APIClaw, and nothing reaches the server without passing your rules. This is the rule we recommend for get_usage_summary:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_usage_summary": {}
  }
}

get_usage_summary is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register APIClaw — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_usage_summary

What does the get_usage_summary tool do? +

Summary of recent workspace usage (calls, providers, cost) for the current billing period. It is categorised as a Read tool in the APIClaw MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_usage_summary? +

Register the APIClaw MCP server in PolicyLayer and add a rule for get_usage_summary: 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 APIClaw. Nothing to install.

What risk level is get_usage_summary? +

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

Can I rate-limit get_usage_summary? +

Yes. Add a rate_limit block to the get_usage_summary 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_summary completely? +

Set action: deny in the PolicyLayer policy for get_usage_summary. 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_summary? +

get_usage_summary is provided by the APIClaw MCP server (nordsym/apiclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every APIClaw tool call.

Start from APIClaw, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

24 APIClaw tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.