Get a specific payment request by ID
AI agents call pex_get_payment_request to retrieve information from PEX 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 information about a payment request using an ID parameter. It queries existing data without creating, modifying, deleting, or executing any business logic. The 'get' verb and retrieval-focused description confirm Read classification. Severity is low because accessing payment request metadata poses minimal risk compared to financial transactions or destructive operations.
From the tool's definition Tool name 'pex_get_payment_request' and description 'Get a specific payment request by ID' indicate retrieval of existing data with no modification or side effects.
Attacks that exploit this kind of access
Get a specific payment request by ID. It is categorised as a Read tool in the PEX MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PEX MCP Server MCP server in PolicyLayer and add a rule for pex_get_payment_request: 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 PEX MCP Server. Nothing to install.
pex_get_payment_request 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 pex_get_payment_request 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 pex_get_payment_request. 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.
pex_get_payment_request is provided by the PEX MCP Server MCP server (pexcard/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 →