get_usage

View your recent tool call history — which tools you called, what methods, how much each cost, and when.

Server AgentPay joepangallo/mcp-server-agentpay
Category Read
Risk class Low
Parameters 00 required

What get_usage does on AgentPay

AI agents call get_usage to retrieve information from AgentPay 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 tool retrieves and displays usage logs and billing history. It performs no modifications, deletions, or external operations. The read-only nature and limited blast radius (exposure of usage metadata) place it in the Read category with low severity.

From the tool's definition Tool description states 'View your recent tool call history' — a retrieval operation with no side effects. It queries historical data about tool calls, costs, and timestamps.

Questions about get_usage

What does the get_usage tool do? +

View your recent tool call history — which tools you called, what methods, how much each cost, and when. It is categorised as a Read tool in the AgentPay MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_usage? +

Register the AgentPay 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 AgentPay. 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 AgentPay MCP server (joepangallo/mcp-server-agentpay). 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.