AI agents use create_hashtag to create or update resources in Filevine — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Filevine environment.
Creating a hashtag is a write operation that creates new, reversible metadata within the Filevine system. It does not execute code, delete data, move money, or have destructive effects. The blast radius of accidental misuse is minimal—creating unwanted tags is easily cleaned up and does not affect case data, financial records, or system integrity.
From the tool's definition Tool description states 'Create a hashtag' which is a write operation that creates new metadata tags for use in notes and tasks. The action is reversible and creates organizational data.
Attacks that exploit this kind of access
Create a hashtag for use in notes and tasks. hashtag is the tag name (without #). It is categorised as a Write tool in the Filevine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Filevine MCP server in PolicyLayer and add a rule for create_hashtag: 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 Filevine. Nothing to install.
create_hashtag 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 create_hashtag 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 create_hashtag. 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.
create_hashtag is provided by the Filevine MCP server (rosenadvertising/filevine-mcp). 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 →