actual_tags_delete
Delete a tag from Actual Budget by its UUID.
This record as markdown: /tools/actual/actual-tags-delete.md
What actual_tags_delete does on Actual
AI agents call actual_tags_delete to permanently remove resources in Actual, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why actual_tags_delete is rated Critical
This tool permanently removes a tag, which is an irreversible operation. Once deleted, the tag cannot be recovered unless explicitly restored through other means. In a financial management system, tags are often used for categorization and organization of transactions; deleting a tag could affect the organization of financial records and reporting.
From the tool's definition Delete a tag from Actual Budget by its UUID — the verb 'Delete' combined with 'from' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs actual_tags_delete 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_tags_delete, this is the rule to start with:
actual_tags_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Actual, apply this rule, and every actual_tags_delete call is checked against it from then on.
Questions about actual_tags_delete
Delete a tag from Actual Budget by its UUID. It is categorised as a Destructive tool in the Actual MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Actual MCP server in PolicyLayer and add a rule for actual_tags_delete: 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_tags_delete is a Destructive 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 actual_tags_delete 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_tags_delete. 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_tags_delete 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.
Across the catalogue