Update an existing payment link by ID. Only provided fields are updated.
AI agents use update_payment_link to create or update resources in Payoza MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Payoza MCP Server environment.
This tool modifies an existing payment link, which is a reversible write operation. It can affect payment flows if misused (e.g., changing amounts or destinations), but does not delete data or directly move funds, making it a Write with medium severity.
From the tool's definition Update an existing payment link by ID. Only provided fields are updated.
Attacks that exploit this kind of access
Update an existing payment link by ID. Only provided fields are updated. It is categorised as a Write tool in the Payoza MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Payoza MCP Server MCP server in PolicyLayer and add a rule for update_payment_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 Payoza MCP Server. Nothing to install.
update_payment_link is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_payment_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 update_payment_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.
update_payment_link is provided by the Payoza MCP Server MCP server (payoza/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 →