Check the status of a transaction by its ID. Use this to poll for approval status after a send that requires human approval.
AI agents call wallet_tx_status to retrieve information from PayPls 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 and queries existing transaction status information. It has no side effects—it does not create, modify, delete, or execute operations. While it operates in a financial system context, the tool itself only reads data; it does not move money, commit financial obligations, or alter any state. The polling mechanism is a passive query against existing transaction records.
From the tool's definition Tool name 'wallet_tx_status' and description 'Check the status of a transaction by its ID' indicate a read-only query operation that retrieves transaction state without modifying data or triggering actions.
Attacks that exploit this kind of access
Check the status of a transaction by its ID. Use this to poll for approval status after a send that requires human approval. It is categorised as a Read tool in the PayPls MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PayPls MCP Server MCP server in PolicyLayer and add a rule for wallet_tx_status: 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 PayPls MCP Server. Nothing to install.
wallet_tx_status 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 wallet_tx_status 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 wallet_tx_status. 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.
wallet_tx_status is provided by the PayPls MCP Server MCP server (n8m8/paypls-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 →