Get an active deep link for a transaction. Returns a clickable URL that redirects to the payware mobile app. Deep Link Format: - Web URL: https://go.payware.eu/{transactionId} - Mobile Redirect: payware://{transactionId} Use Cases: - P2P payments via messaging services - Mobile-only e-commerce pa...
AI agents call payware_deep_links_get_transaction_link 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 tool performs a query operation that fetches a pre-generated deep link URL for an already-existing transaction. It has no side effects, does not create, modify, or delete data, and does not move money or execute arbitrary code.
From the tool's definition Tool 'payware_deep_links_get_transaction_link' retrieves and returns 'a clickable URL that redirects to the payware mobile app' for an existing transaction.
Attacks that exploit this kind of access
Get an active deep link for a transaction. Returns a clickable URL that redirects to the payware mobile app. Deep Link Format: - Web URL: https://go.payware.eu/{transactionId} - Mobile Redirect: payware://{transactionId} Use Cases: - P2P payments via messaging services - Mobile-only e-commerce payments - Advertisement references Important Notes: - Deep links are only supported in production environment - Link expiration is synchronized with the referenced transaction - Traditional deep links that route to app content when app is installed. 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_deep_links_get_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_get_transaction_link 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_deep_links_get_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_get_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_get_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 →