set_org_member_role · Run402 MCP: Risk & Policy

WHAT IT DOES

What set_org_member_role does on Run402

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

WHY IT NEEDS A POLICY

Why set_org_member_role needs a policy

This tool modifies organizational membership attributes (role assignment) reversibly. It is not destructive (the member is not removed), not financial, and not execute/read. However, it has high severity because role changes can grant or revoke significant access—a misuse could escalate privileges, lock out legitimate users, or grant unauthorized permissions to agents.

From the tool's definition Tool name 'set_org_member_role' with description 'Change a member' modifies user roles/permissions within an organization.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_org_member_role Rate-limited

set_org_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": {
    "set_org_member_role": {
      "limits": [
        {
          "counter": "set_org_member_role_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 Run402, so you can run agents against it safely.

FAQ

Questions about set_org_member_role

What does the set_org_member_role tool do? +

Change a member. It is categorised as a Write tool in the Run402 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_org_member_role? +

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

What risk level is set_org_member_role? +

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

Can I rate-limit set_org_member_role? +

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

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

set_org_member_role is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.