AI agents use add_contact_to_project 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 creates or modifies an association between a contact and a project, which is reversible data modification. It does not execute arbitrary code, delete data, or move money. The 'medium' severity reflects that misconfiguration could expose a contact's information to unauthorized project members in a legal case management system, but the blast radius is limited to project membership changes.
From the tool's definition add_contact_to_project with description 'Add a contact to a project with an optional role' clearly modifies project data by associating a contact record with a project.
Attacks that exploit this kind of access
Add a contact to a project with an optional role. 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 add_contact_to_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.
add_contact_to_project 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 add_contact_to_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 add_contact_to_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.
add_contact_to_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 →