Retrieve recent transaction usage. Requires an account-level API key.
AI agents call mailosaur_usage_transactions to retrieve information from Mailosaur MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries transaction history/usage data without modifying, deleting, or executing operations. It is a straightforward data retrieval function. The severity is low because viewing usage/transaction records poses minimal risk even if accessed by an unauthorized agent—it provides informational data about account consumption but does not expose financial transactions, enable account modifications, or trigger…
From the tool's definition Tool name 'mailosaur_usage_transactions' and description 'Retrieve recent transaction usage' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Retrieve recent transaction usage. Requires an account-level API key. It is categorised as a Read tool in the Mailosaur MCP MCP Server, which means it retrieves data without modifying state.
Register the Mailosaur MCP server in PolicyLayer and add a rule for mailosaur_usage_transactions: 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 Mailosaur MCP. Nothing to install.
mailosaur_usage_transactions 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 mailosaur_usage_transactions 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 mailosaur_usage_transactions. 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.
mailosaur_usage_transactions is provided by the Mailosaur MCP server (mrnewdelhi/mailosaur-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 →