add_workspace_member
Add an existing org user to a workspace with a role. Requires a UUID user_id; use list_all_users to find it, and invite_user first if the person is not yet in the org.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/add-workspace-member.md
What add_workspace_member does on Portkey Admin
AI agents use add_workspace_member to create or update resources in Portkey Admin, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Portkey Admin environment.
Why add_workspace_member is rated Medium
The tool creates a new workspace member assignment, which is a Write operation (reversible configuration change). Severity is medium because incorrect role assignment could grant unintended access permissions, but the action can be undone by removing the member. Confidence is high because the description clearly indicates a create/modify action on workspace membership data.
From the tool's definition Tool description states 'Add an existing org user to a workspace with a role' - this creates or modifies workspace membership, a reversible data change.
Attacks that exploit this kind of access
The rule that runs add_workspace_member safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Portkey Admin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_workspace_member, this is the rule to start with:
add_workspace_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Portkey Admin, apply this rule, and every add_workspace_member call is checked against it from then on.
Questions about add_workspace_member
Add an existing org user to a workspace with a role. Requires a UUID user_id; use list_all_users to find it, and invite_user first if the person is not yet in the org. It is categorised as a Write tool in the Portkey Admin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for add_workspace_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 Portkey Admin. Nothing to install.
add_workspace_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 add_workspace_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 add_workspace_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.
add_workspace_member is provided by the Portkey Admin MCP server (codeswhat/portkey-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Portkey Admin, and thousands of servers like it.
This server
Across the catalogue