Fetch one mandate by id, with live spend counters.
AI agents call payments_mandates_get to retrieve information from Mailgent MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves mandate information and associated spend counters. It has no side effects—it queries existing data without creating, modifying, or deleting anything. The mention of 'spend counters' does not elevate it to Financial category because it only reads balances rather than moving money or committing financial obligations.
From the tool's definition Tool name includes 'get' and description states 'Fetch one mandate by id' — both indicating data retrieval without modification. The term 'fetch' explicitly signals read-only querying.
Attacks that exploit this kind of access
Fetch one mandate by id, with live spend counters. It is categorised as a Read tool in the Mailgent MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mailgent MCP Server MCP server in PolicyLayer and add a rule for payments_mandates_get: 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 Mailgent MCP Server. Nothing to install.
payments_mandates_get 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 payments_mandates_get 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 payments_mandates_get. 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.
payments_mandates_get is provided by the Mailgent MCP Server MCP server (loomal-ai/loomal-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 →