Get status of an ACTIVE transaction by ID (for completed/expired transactions use transaction history tool). Endpoint: GET /transactions/{transactionId} Use Case: Check status of ACTIVE transactions only. This endpoint only returns transactions with ACTIVE status. Note: For transactions with fina...
AI agents call payware_operations_get_transaction_status to retrieve information from Payware MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that retrieves transaction status without side effects. While it accesses payment-related data (which could be sensitive), the tool itself performs no destructive, write, execute, or financial operations.
From the tool's definition Tool description explicitly states 'Get status of an ACTIVE transaction by ID' and uses GET endpoint to retrieve transaction data.
Attacks that exploit this kind of access
Get status of an ACTIVE transaction by ID (for completed/expired transactions use transaction history tool). Endpoint: GET /transactions/{transactionId} Use Case: Check status of ACTIVE transactions only. This endpoint only returns transactions with ACTIVE status. Note: For transactions with final statuses (CONFIRMED, DECLINED, FAILED, EXPIRED, CANCELLED), use. It is categorised as a Read tool in the Payware MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Payware MCP Server MCP server in PolicyLayer and add a rule for payware_operations_get_transaction_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 Payware MCP Server. Nothing to install.
payware_operations_get_transaction_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 payware_operations_get_transaction_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 payware_operations_get_transaction_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.
payware_operations_get_transaction_status is provided by the Payware MCP Server MCP server (payware/mcp-server). 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 →