Update an existing recurrence — change amount, card (storageCard), end date, or pause/resume. Pass only the fields you want to change.
AI agents use update_recurrence to commit financial operations through Mcp Ap2 — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool modifies recurring financial payment schedules, including changing the payment amount and payment card. Altering recurring payment configurations directly impacts financial obligations, making this a Financial category tool with critical severity since an AI agent could increase payment amounts, swap payment methods, or manipulate billing cycles.
From the tool's definition Update an existing recurrence — change amount, card (storageCard), end date, or pause/resume
Documented attack patterns abuse exactly the kind of access update_recurrence 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_recurrence:
{
"version": "1",
"default": "deny",
"tools": {
"update_recurrence": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to update_recurrence is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Update an existing recurrence — change amount, card (storageCard), end date, or pause/resume. Pass only the fields you want to change. It is categorised as a Financial tool in the Mcp Ap2 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for update_recurrence: 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_recurrence is a Financial 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 update_recurrence 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_recurrence. 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_recurrence 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.