AI agents call get_payment to retrieve information from Moneroo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves payment transaction data by ID. It performs a passive data lookup with no side effects, no ability to modify or delete data, and no financial transactions. It is clearly a Read operation. Severity is low because unauthorized access to individual payment records, while a privacy concern, has limited blast radius compared to bulk operations or financial modifications.
From the tool's definition Tool name 'get_payment' and description 'Retrieve the full details of a payment transaction by its ID' indicate a read-only query operation that fetches existing data without modification, deletion, or financial action.
Attacks that exploit this kind of access
Retrieve the full details of a payment transaction by its ID. It is categorised as a Read tool in the Moneroo MCP Server, which means it retrieves data without modifying state.
Register the Moneroo MCP server in PolicyLayer and add a rule for get_payment: 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 Moneroo. Nothing to install.
get_payment 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_payment 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_payment. 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_payment is provided by the Moneroo MCP server (moneroo-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 →