update_team_member
AI agents use update_team_member to create or update resources in Multilead Open API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Multilead Open API MCP Server environment.
The 'update_team_member' tool modifies existing team member records (reversible changes). Without description detail, the exact scope of updates is unclear—could range from profile fields to permissions—but the semantic strongly indicates Write rather than Execute or Destructive.
From the tool's definition Tool name 'update_team_member' indicates modification of team member data. The description is empty, limiting direct confirmation of scope.
Attacks that exploit this kind of access
update_team_member. It is categorised as a Write tool in the Multilead Open API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Multilead Open API MCP Server MCP server in PolicyLayer and add a rule for update_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 Multilead Open API MCP Server. Nothing to install.
update_team_member 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 update_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.
Set action: deny in the PolicyLayer policy for update_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.
update_team_member is provided by the Multilead Open API MCP Server MCP server (vanman2024/multilead-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 →