Create, update, or delete a single scheduled (recurring) transaction. Use this to manage recurring bills or savings transfers.
AI agents use manage-scheduled-transaction to create or update resources in You Need A Budget (YNAB) MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your You Need A Budget (YNAB) MCP environment.
Although the tool can delete scheduled transactions (which is destructive), the primary use case emphasizes creation and updating of recurring transactions. The tool is classified as Write rather than Destructive because: (1) the emphasis in the description is on management/creation/updating, (2) deletions of scheduled transactions could theoretically be recreated if needed, and (3) it does not directly move money…
From the tool's definition Tool description states it can 'Create, update, or delete a single scheduled (recurring) transaction.' The delete operation is destructive in nature, but the tool's primary design intent (as evidenced by emphasis on 'manage recurring bills or savings…
Documented attack patterns abuse exactly the kind of access manage-scheduled-transaction gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and You Need A Budget (YNAB) MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for manage-scheduled-transaction:
{
"version": "1",
"default": "deny",
"tools": {
"manage-scheduled-transaction": {
"limits": [
{
"counter": "manage-scheduled-transaction_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} manage-scheduled-transaction 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.
Create, update, or delete a single scheduled (recurring) transaction. Use this to manage recurring bills or savings transfers. It is categorised as a Write tool in the You Need A Budget (YNAB) MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the You Need A Budget (YNAB) MCP server in PolicyLayer and add a rule for manage-scheduled-transaction: 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 You Need A Budget (YNAB) MCP. Nothing to install.
manage-scheduled-transaction 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 manage-scheduled-transaction 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 manage-scheduled-transaction. 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.
manage-scheduled-transaction is provided by the You Need A Budget (YNAB) MCP server (jtewen/ynab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from You Need A Budget (YNAB) MCP, 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.
14 You Need A Budget (YNAB) MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.