update_mcp_server_user_access
Grant or revoke individual user access to an MCP server. Changes take effect immediately and override the default access setting for the selected users; use list_mcp_server_user_access first if you need the current state.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/update-mcp-server-user-access.md
What update_mcp_server_user_access does on Portkey Admin
AI agents use update_mcp_server_user_access 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 update_mcp_server_user_access is rated Medium
This tool creates or modifies user access permissions to MCP servers. While it affects authorization rather than data, it is reversible (access can be granted or revoked), making it a Write operation rather than Destructive. The severity is high because misconfiguration could grant unauthorized access to sensitive systems or revoke legitimate access, creating security and availability risks.
From the tool's definition Tool explicitly performs 'Grant or revoke individual user access' and 'Changes take effect immediately', indicating it modifies access control state for users.
Attacks that exploit this kind of access
The rule that runs update_mcp_server_user_access 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 update_mcp_server_user_access, this is the rule to start with:
update_mcp_server_user_access 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 update_mcp_server_user_access call is checked against it from then on.
Questions about update_mcp_server_user_access
Grant or revoke individual user access to an MCP server. Changes take effect immediately and override the default access setting for the selected users; use list_mcp_server_user_access first if you need the current state. 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 update_mcp_server_user_access: 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.
update_mcp_server_user_access 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_mcp_server_user_access 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_mcp_server_user_access. 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_mcp_server_user_access 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