Busca detalhes de um pedido no Pagar.me V5 pelo ID do pedido (ex: or_xxxxxxxx).
AI agents call pagarme_get_order to retrieve information from Payments MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves order details by ID from the Pagar.me payment system. It is a read-only operation that does not create, modify, delete, or execute any actions. While it operates in a financial context (payment orders), the tool itself only queries and returns information. The financial category applies to tools that move money or commit financial obligations; this tool merely accesses existing order data.
From the tool's definition Tool name 'pagarme_get_order' and description 'Busca detalhes de um pedido' (retrieves order details) indicate a query/fetch operation that retrieves data without modifying or executing anything. No side effects.
Attacks that exploit this kind of access
Busca detalhes de um pedido no Pagar.me V5 pelo ID do pedido (ex: or_xxxxxxxx). It is categorised as a Read tool in the Payments MCP MCP Server, which means it retrieves data without modifying state.
Register the Payments MCP server in PolicyLayer and add a rule for pagarme_get_order: 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 Payments MCP. Nothing to install.
pagarme_get_order 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 pagarme_get_order 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 pagarme_get_order. 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.
pagarme_get_order is provided by the Payments MCP server (lpillonwp/mcp-payments). 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 →