organizations_change_member_role
Run organizations.change-member-role through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/organizations-change-member-role.md
What organizations_change_member_role does on Appaloft
AI agents use organizations_change_member_role to create or update resources in Appaloft, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Appaloft environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
role | string | Yes | |
memberId | string | Yes | |
idempotencyKey | string | — | |
organizationId | string | Yes |
Parameters from the server's own tool schema.
Why organizations_change_member_role is rated Medium
Changing a member's role is a reversible modification of access/permission data within an organization. It does not delete data or execute code, making Write the most appropriate category. Severity is medium because misconfigured roles could grant unintended privileges, but the action is reversible.
From the tool's definition organizations.change-member-role — changes a member's role within an organization
Attacks that exploit this kind of access
The rule that runs organizations_change_member_role safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For organizations_change_member_role, this is the rule to start with:
organizations_change_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every organizations_change_member_role call is checked against it from then on.
Questions about organizations_change_member_role
Run organizations.change-member-role through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Write tool in the Appaloft MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
organizations_change_member_role accepts 4 parameters: role, memberId, idempotencyKey, organizationId. Required: role, memberId, organizationId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for organizations_change_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 Appaloft. Nothing to install.
organizations_change_member_role 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 organizations_change_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.
Set action: deny in the PolicyLayer policy for organizations_change_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.
organizations_change_member_role is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
This server
Across the catalogue