update_member_role

Changes a member's role within an organization. Cannot change your own role or the owner's role. Requires admin scope and admin or owner role.

SERVERagentView SOURCEhttps://agentview.de/mcp

Medium RISK CLASS

Category Write

Parameters 43 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/de-agentview-agentview-mcp/update-member-role.md

WHAT IT DOES

What update_member_role does on agentView

AI agents use update_member_role to create or update resources in agentView, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your agentView environment.

Parameter	Type	Required	Description
`role`	string	Yes	The new role. Valid roles depend on organization type (e.g. 'admin', 'manager', 'viewer').
`org_id`	string	Yes	The organization ID.
`access_token`	string	—	Optional JWT access token for authentication.
`target_user_id`	string	Yes	The user ID of the member whose role to change.

Parameters from the server's own tool schema.

RISK

Why update_member_role is rated Medium

This is a Write operation because it modifies organizational data (member roles) reversibly. While it can significantly impact user access and permissions, roles are changeable and the tool has built-in safeguards.

From the tool's definition Tool description states 'Changes a member's role within an organization', which is a modification operation. The tool modifies organizational access control and permissions, which are reversible (roles can be changed again), not permanent deletion.

Risk signalsHandles credentials or secrets (access_token) · Admin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_member_role safely

PolicyLayer is an MCP gateway: it sits between your AI agents and agentView, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_member_role, this is the rule to start with:

update_member_role Rate-limited

update_member_role 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_member_role": {
      "limits": [
        {
          "counter": "update_member_role_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect agentView, apply this rule, and every update_member_role call is checked against it from then on.

FAQ

Questions about update_member_role

What does the update_member_role tool do? +

Changes a member's role within an organization. Cannot change your own role or the owner's role. Requires admin scope and admin or owner role. It is categorised as a Write tool in the agentView MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_member_role accept? +

update_member_role accepts 4 parameters: role, org_id, access_token, target_user_id. Required: role, org_id, target_user_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_member_role? +

Register the agentView MCP server in PolicyLayer and add a rule for update_member_role: 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 agentView. Nothing to install.

What risk level is update_member_role? +

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

Can I rate-limit update_member_role? +

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

Set action: deny in the PolicyLayer policy for update_member_role. 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_member_role? +

update_member_role is provided by the agentView MCP server (https://agentview.de/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on agentView, and thousands of servers like it.

This server

All 79 agentView tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →