updateProject
Update a project's name, description, and/or icon. Mirrors the UI Project General Settings page. Auth: admin on the project (cascades from workspace owner/admin and org admin). Partial updates; at least one of name/description/icon must be supplied. Rate limit 60/min.
This record as markdown: /tools/io-stablebaseline-sb/updateproject.md
What updateProject does on Stable Baseline
AI agents use updateProject 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 |
|---|---|---|---|
icon | string | null | — | Pass null to clear. |
name | string | — | |
project_id | string | Yes | Project UUID. |
description | string | null | — | Pass null to clear. |
Parameters from the server's own tool schema.
Why updateProject is rated Medium
This tool creates or modifies project metadata reversibly (name, description, icon). Updates can be undone by subsequent calls. It requires admin-level authorization (project, workspace, or org admin), which limits but does not eliminate risk.
From the tool's definition Tool description states 'Update a project's name, description, and/or icon' and 'Partial updates' — these are reversible modifications to project metadata. The tool mirrors UI settings functionality rather than executing arbitrary operations or deleting data.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs updateProject 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 updateProject, this is the rule to start with:
updateProject 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 updateProject call is checked against it from then on.
Questions about updateProject
Update a project's name, description, and/or icon. Mirrors the UI Project General Settings page. Auth: admin on the project (cascades from workspace owner/admin and org admin). Partial updates; at least one of name/description/icon must be supplied. Rate limit 60/min. 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.
updateProject accepts 4 parameters: icon, name, project_id, description. Required: project_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 updateProject: 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.
updateProject 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 updateProject 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 updateProject. 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.
updateProject 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