create_schedule · Actual Budget MCP Server MCP

WHAT IT DOES

What create_schedule does on Actual Budget MCP Server

AI agents use create_schedule to create or update resources in Actual Budget MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Actual Budget MCP Server environment.

WHY IT NEEDS A POLICY

Why create_schedule needs a policy

This tool creates a new scheduled/recurring transaction in the budget system. It's a write operation that adds data reversibly (the sibling tool 'delete_schedule' can undo it). While it involves financial data, it doesn't move real money or commit actual financial obligations — it only records planned transactions within the budgeting app.

From the tool's definition Create a new scheduled/recurring transaction. Great for setting up recurring bills, subscriptions, or regular income.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_schedule Rate-limited

create_schedule 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_schedule": {
      "limits": [
        {
          "counter": "create_schedule_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Actual Budget MCP Server, so you can run agents against it safely.

FAQ

Questions about create_schedule

What does the create_schedule tool do? +

Create a new scheduled/recurring transaction. Great for setting up recurring bills, subscriptions, or regular income. It is categorised as a Write tool in the Actual Budget MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_schedule? +

Register the Actual Budget MCP Server MCP server in PolicyLayer and add a rule for create_schedule: 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 Actual Budget MCP Server. Nothing to install.

What risk level is create_schedule? +

create_schedule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_schedule? +

Yes. Add a rate_limit block to the create_schedule 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.

How do I block create_schedule completely? +

Set action: deny in the PolicyLayer policy for create_schedule. 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.

What MCP server provides create_schedule? +

create_schedule is provided by the Actual Budget MCP Server MCP server (yhc0712/actual-budget-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.