actual_categories_create
Create a category. REQUIRED: group_id (category group UUID). Use actual_category_groups_get to find available groups. Optional: is_income (boolean, defaults to false for expense categories).
This record as markdown: /tools/actual/actual-categories-create.md
What actual_categories_create does on Actual
AI agents use actual_categories_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_categories_create is rated Medium
Creating a category is a reversible write operation that modifies the financial data structure. While it doesn't cause irreversible deletion (Destructive) or move money (Financial), it does create persistent data in a financial system which warrants medium severity due to potential downstream effects on budgeting and financial tracking. The operation can be undone through deletion.
From the tool's definition Tool description states "Create a category" which creates data in the financial management system.
Attacks that exploit this kind of access
The rule that runs actual_categories_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_categories_create, this is the rule to start with:
actual_categories_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_categories_create call is checked against it from then on.
Questions about actual_categories_create
Create a category. REQUIRED: group_id (category group UUID). Use actual_category_groups_get to find available groups. Optional: is_income (boolean, defaults to false for expense categories). 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_categories_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_categories_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_categories_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_categories_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_categories_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