actual_tags_list
List all tags defined in Actual Budget. Tags are stored without a leading
This record as markdown: /tools/actual/actual-tags-list.md
What actual_tags_list does on Actual
AI agents call actual_tags_list to retrieve information from Actual without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why actual_tags_list is rated Low
This tool retrieves and enumerates existing tags from the budget system. It is a pure read operation that queries data without creating, modifying, deleting, or executing any changes. The verb 'List' is characteristic of Read category tools.
From the tool's definition Tool name 'actual_tags_list' and description 'List all tags defined in Actual Budget' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs actual_tags_list 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_list, this is the rule to start with:
actual_tags_list is read-only, so it stays allowed. 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_tags_list call is checked against it from then on.
Questions about actual_tags_list
List all tags defined in Actual Budget. Tags are stored without a leading. It is categorised as a Read tool in the Actual MCP Server, which means it retrieves data without modifying state.
Register the Actual MCP server in PolicyLayer and add a rule for actual_tags_list: 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_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the actual_tags_list 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_list. 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_list 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