Delete an active deep link for a transaction on behalf of a merchant. Once deleted, the deep link URL will no longer redirect to the payware mobile app. ISV Authentication: - Requires ISV JWT token with merchant partner ID in
AI agents call payware_deep_links_delete_transaction_link 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.
This tool destroys active transaction deep links without reversibility. While not directly moving money, it operates within a payment processing system and could disrupt legitimate payment flows or merchant operations if misused by an agent. The Destructive category applies because the deletion is permanent and cannot be undone.
From the tool's definition Tool performs irreversible deletion of a transaction deep link: 'Delete an active deep link for a transaction' with 'the deep link URL will no longer redirect'. Once deleted, the resource cannot be recovered.
Attacks that exploit this kind of access
Delete an active deep link for a transaction on behalf of a merchant. Once deleted, the deep link URL will no longer redirect to the payware mobile app. ISV Authentication: - Requires ISV JWT token with merchant partner ID in. 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.
Register the Payware MCP Server MCP server in PolicyLayer and add a rule for payware_deep_links_delete_transaction_link: 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_deep_links_delete_transaction_link is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the payware_deep_links_delete_transaction_link 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_deep_links_delete_transaction_link. 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_deep_links_delete_transaction_link 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 →