Remove a contact from a project.
AI agents call remove_contact_from_project to permanently remove resources in Filevine — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a contact from a project is likely an irreversible or difficult-to-reverse action in a legal case management system. Unlike 'update' or 'archive', removal of a contact association could sever important legal relationships and audit trails. The inverse operation (add_contact_to_project) exists, but data such as role history or timestamps of the original association may be permanently lost.
From the tool's definition "Remove a contact from a project" - the word 'remove' indicates deletion of an association between a contact and a project
Attacks that exploit this kind of access
Remove a contact from a project. It is categorised as a Destructive tool in the Filevine MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Filevine MCP server in PolicyLayer and add a rule for remove_contact_from_project: 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_contact_from_project 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 remove_contact_from_project 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_contact_from_project. 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_contact_from_project 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 →