AI agents use remove_tag_from_documents 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.
This tool modifies metadata (tags) on documents by removing a tag from all documents that have it. While tag removal is technically reversible (the tag could be re-added), it affects potentially many documents at once with a broad blast radius. It falls under Write as tag removal is a metadata modification rather than document deletion, but the bulk nature ('all documents') makes severity high.
From the tool's definition Remove a tag from all documents that have it
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Remove a tag from all documents that have it. 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 remove_tag_from_documents: 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.
remove_tag_from_documents 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 remove_tag_from_documents 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 remove_tag_from_documents. 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.
remove_tag_from_documents 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 →