update_project_team_member · Filevine MCP: Risk & Policy

WHAT IT DOES

What update_project_team_member does on Filevine

AI agents use update_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 update_project_team_member needs a policy

Updating a team member's role is a reversible modification operation. While it could affect access control and permissions within a legal case management system, the change can be undone by updating the role again. This is a Write operation (modify data reversibly) rather than Execute (which would involve running arbitrary code or operations with unpredictable effects).

From the tool's definition Tool name contains 'update' and description states 'Update a team member's role on a project.' This modifies existing data (team member role assignment) reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_project_team_member Rate-limited

update_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": {
    "update_project_team_member": {
      "limits": [
        {
          "counter": "update_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 update_project_team_member

What does the update_project_team_member tool do? +

Update a team member's role on 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 update_project_team_member? +

Register the Filevine MCP server in PolicyLayer and add a rule for update_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 update_project_team_member? +

update_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 update_project_team_member? +

Yes. Add a rate_limit block to the update_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 update_project_team_member completely? +

Set action: deny in the PolicyLayer policy for update_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 update_project_team_member? +

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