Poll a MoonPay transaction by id. Returns status (pending, processing, completed, failed) and the on-chain tx hash once settled.
AI agents call moonpay_get_transaction to retrieve information from Execution Market without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool purely queries transaction status from MoonPay without creating, updating, deleting, or moving funds. While it operates in a financial context, it does not itself move money or commit financial obligations—it only reads and returns transaction data. This is a Read operation with low severity: misuse would expose transaction details but cannot directly cause financial harm or side effects.
From the tool's definition Tool performs polling and status retrieval: 'Poll a MoonPay transaction by id. Returns status (pending, processing, completed, failed) and the on-chain tx hash once settled.' This is a query operation that retrieves transaction state without modifying,…
Attacks that exploit this kind of access
Poll a MoonPay transaction by id. Returns status (pending, processing, completed, failed) and the on-chain tx hash once settled. It is categorised as a Read tool in the Execution Market MCP Server, which means it retrieves data without modifying state.
Register the Execution Market MCP server in PolicyLayer and add a rule for moonpay_get_transaction: 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 Execution Market. Nothing to install.
moonpay_get_transaction 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 moonpay_get_transaction 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 moonpay_get_transaction. 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.
moonpay_get_transaction is provided by the Execution Market MCP server (https://mcp.execution.market/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 →