Update a Transak order after creation. Used for partner-side post-creation actions such as marking a SELL crypto deposit transaction hash, attaching/changing the partnerCustomerId, refreshing the redirectURL, or correcting the buyer email before KYC. Only mutable fields are accepted; immutable fi...
AI agents use update_order to create or update resources in Mcp Ap2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ap2 environment.
The tool modifies mutable fields of cryptocurrency/fiat payment orders after creation, including customer identifiers, email addresses, and transaction hashes. While these are reversible changes (Write rather than Destructive), the context of a financial payment protocol and the ability to alter order details like buyer email and deposit transaction tracking represent a high-severity Write operation due to potential…
From the tool's definition Tool description explicitly states it is used to 'update' and 'marking', 'attaching', 'changing', 'refreshing', and 'correcting' order fields.
Documented attack patterns abuse exactly the kind of access update_order gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for update_order:
{
"version": "1",
"default": "deny",
"tools": {
"update_order": {
"limits": [
{
"counter": "update_order_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_order stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update a Transak order after creation. Used for partner-side post-creation actions such as marking a SELL crypto deposit transaction hash, attaching/changing the partnerCustomerId, refreshing the redirectURL, or correcting the buyer email before KYC. Only mutable fields are accepted; immutable fields (amount, currency, network) require a fresh order. It is categorised as a Write tool in the Mcp Ap2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for update_order: 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 Mcp Ap2. Nothing to install.
update_order 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_order 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_order. 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_order is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.