Create a new tag for labeling transactions.
AI agents use firefly_create_tag to create or update resources in Firefly III MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Firefly III MCP Server environment.
This tool creates a new tag, which is a reversible write operation. Tags are metadata used to organize and label transactions. Creating a tag has minimal direct financial impact—it does not move money, execute code, or irreversibly delete data. The operation is fully reversible through deletion.
From the tool's definition Tool name contains 'create' and description states 'Create a new tag for labeling transactions.' This adds a new tag entity to the Firefly III system.
Attacks that exploit this kind of access
Create a new tag for labeling transactions. It is categorised as a Write tool in the Firefly III MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Firefly III MCP Server MCP server in PolicyLayer and add a rule for firefly_create_tag: 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 Firefly III MCP Server. Nothing to install.
firefly_create_tag 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 firefly_create_tag 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 firefly_create_tag. 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.
firefly_create_tag is provided by the Firefly III MCP Server MCP server (przbadu/firefly-iii-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →