actual_schedules_create
Create a new schedule in Actual Budget. Schedules can be one-off (supply a YYYY-MM-DD date string) or recurring (supply a RecurConfig object with frequency, start, and endMode). Amounts are in cents — negative for expenses, positive for income.
This record as markdown: /tools/actual/actual-schedules-create.md
What actual_schedules_create does on Actual
AI agents use actual_schedules_create to create or update resources in Actual, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Actual environment.
Why actual_schedules_create is rated Medium
This tool creates new financial schedules (recurring or one-off transactions) in a budget application. It modifies financial data reversibly—new schedules can be edited or deleted later. While it involves financial data, it does not directly move money or commit financial obligations (that would be the execution/posting of the schedule itself).
From the tool's definition Tool name includes 'create' and description states 'Create a new schedule in Actual Budget.' It accepts financial data (amounts in cents, frequency, dates) and creates new records in a financial management system.
Attacks that exploit this kind of access
The rule that runs actual_schedules_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Actual, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For actual_schedules_create, this is the rule to start with:
actual_schedules_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Actual, apply this rule, and every actual_schedules_create call is checked against it from then on.
Questions about actual_schedules_create
Create a new schedule in Actual Budget. Schedules can be one-off (supply a YYYY-MM-DD date string) or recurring (supply a RecurConfig object with frequency, start, and endMode). Amounts are in cents — negative for expenses, positive for income. It is categorised as a Write tool in the Actual MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Actual MCP server in PolicyLayer and add a rule for actual_schedules_create: 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. Nothing to install.
actual_schedules_create 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 actual_schedules_create 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 actual_schedules_create. 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.
actual_schedules_create is provided by the Actual MCP server (actual-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Actual, and thousands of servers like it.
This server
Across the catalogue