updateProfile
Update a member's display name. Your own name needs no organisation_id; another member's name needs organisation_id and the can_manage_members capability. This tool never changes an email address, your own or another member's: only the person can change their own email address, from their Profile...
This record as markdown: /tools/io-stablebaseline-sb/updateprofile.md
What updateProfile does on Stable Baseline
AI agents use updateProfile to create or update resources in Stable Baseline, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stable Baseline environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | |
email | string | — | Leave this out: this tool never changes an email address. A call that names another member's email, or a new email of your own, is refused; each person changes |
user_id | string | Yes | |
organisation_id | string | — | Required when changing another member's name. |
Parameters from the server's own tool schema.
Why updateProfile is rated Medium
An AI agent can call updateProfile faster than any human can review: one bad instruction and it creates or modifies resources in Stable Baseline by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs updateProfile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For updateProfile, this is the rule to start with:
updateProfile 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 Stable Baseline, apply this rule, and every updateProfile call is checked against it from then on.
Questions about updateProfile
Update a member's display name. Your own name needs no organisation_id; another member's name needs organisation_id and the can_manage_members capability. This tool never changes an email address, your own or another member's: only the person can change their own email address, from their Profile page, where a change of the sign-in address is confirmed by email. It is categorised as a Write tool in the Stable Baseline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
updateProfile accepts 4 parameters: name, email, user_id, organisation_id. Required: user_id. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for updateProfile: 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 Stable Baseline. Nothing to install.
updateProfile 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 updateProfile 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 updateProfile. 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.
updateProfile is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue