Get transaction details for a specific transaction by ID
AI agents call pex_get_transaction_detail 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 transaction information by ID without creating, modifying, deleting, or executing any operations. It is a simple read operation that queries existing financial transaction data. The blast radius of misuse is limited to unauthorized information disclosure of transaction details, which is lower severity than tools that could modify accounts, execute transfers, or delete data.
From the tool's definition Tool name 'pex_get_transaction_detail' uses 'get' verb and description states 'Get transaction details for a specific transaction by ID' — both indicate retrieval only with no modification or side effects.
Attacks that exploit this kind of access
Get transaction details for a specific transaction 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_transaction_detail: 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_transaction_detail 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_transaction_detail 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_transaction_detail. 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_transaction_detail 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 →