Get the current billing cycle usage for the account (sending and testing plans, limits, and current counts).
AI agents call get-billing-usage to retrieve information from Mcp Mailtrap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and returns billing usage information without modifying, deleting, or creating any data. While it relates to billing, it does not move money or commit financial obligations—it merely reads the current state of the account's billing metrics. This is a straightforward Read operation with minimal risk.
From the tool's definition The tool 'get-billing-usage' performs a 'Get' operation that retrieves 'the current billing cycle usage for the account' including 'limits and current counts'. This is a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the current billing cycle usage for the account (sending and testing plans, limits, and current counts). It is categorised as a Read tool in the Mcp Mailtrap MCP Server, which means it retrieves data without modifying state.
Register the Mcp Mailtrap MCP server in PolicyLayer and add a rule for get-billing-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 Mcp Mailtrap. Nothing to install.
get-billing-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-billing-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-billing-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-billing-usage is provided by the Mcp Mailtrap MCP server (mcp-mailtrap). 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 →