remove_project_team_member · Filevine MCP: Risk & Policy

WHAT IT DOES

What remove_project_team_member does on Filevine

AI agents use remove_project_team_member 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.

WHY IT NEEDS A POLICY

Why remove_project_team_member needs a policy

Removing a team member from a project modifies access/membership data. While potentially reversible (the member could be re-added using add_team_member_to_project), it changes project access controls and could disrupt legal case management workflows. Classified as Write rather than Destructive because the action is reversible via the sibling add_team_member_to_project tool.

From the tool's definition Remove a team member from a project

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_project_team_member Rate-limited

remove_project_team_member stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "remove_project_team_member": {
      "limits": [
        {
          "counter": "remove_project_team_member_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Filevine, so you can run agents against it safely.

FAQ

Questions about remove_project_team_member

What does the remove_project_team_member tool do? +

Remove a team member from a project. 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.

How do I enforce a policy on remove_project_team_member? +

Register the Filevine MCP server in PolicyLayer and add a rule for remove_project_team_member: 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.

What risk level is remove_project_team_member? +

remove_project_team_member is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit remove_project_team_member? +

Yes. Add a rate_limit block to the remove_project_team_member 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.

How do I block remove_project_team_member completely? +

Set action: deny in the PolicyLayer policy for remove_project_team_member. 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.

What MCP server provides remove_project_team_member? +

remove_project_team_member 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.