payware_operations_cancel_transaction

Cancel an active transaction as an ISV on behalf of a merchant. Requires ISV authentication with merchant partner ID and OAuth2 token. Only ACTIVE transactions can be cancelled.

Server Payware MCP Server payware/mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What payware_operations_cancel_transaction does on Payware MCP Server

AI agents call payware_operations_cancel_transaction to permanently remove resources in Payware MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why payware_operations_cancel_transaction needs a policy

Although the tool does not physically delete data from a database, cancelling a transaction is a destructive financial operation that irreversibly alters the state of a live payment. The action has real-world financial consequences (refunds, revenue impact, customer disputes) and cannot be automatically reversed.

From the tool's definition The tool is described as 'Cancel an active transaction' which irreversibly terminates an active payment transaction.

Questions about payware_operations_cancel_transaction

What does the payware_operations_cancel_transaction tool do? +

Cancel an active transaction as an ISV on behalf of a merchant. Requires ISV authentication with merchant partner ID and OAuth2 token. Only ACTIVE transactions can be cancelled. It is categorised as a Destructive tool in the Payware MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on payware_operations_cancel_transaction? +

Register the Payware MCP Server MCP server in PolicyLayer and add a rule for payware_operations_cancel_transaction: 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.

What risk level is payware_operations_cancel_transaction? +

payware_operations_cancel_transaction is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit payware_operations_cancel_transaction? +

Yes. Add a rate_limit block to the payware_operations_cancel_transaction 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.

How do I block payware_operations_cancel_transaction completely? +

Set action: deny in the PolicyLayer policy for payware_operations_cancel_transaction. 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.

What MCP server provides payware_operations_cancel_transaction? +

payware_operations_cancel_transaction 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.