createProject
Create a new project inside a workspace. Mirrors the UI Create Project dialog. Auth: write on workspace + credential's can_lifecycle capability. Validates name (1..200) and description (0..2000); icon defaults to a folder emoji if omitted. The plan's project limit is checked on the server. Rate l...
This record as markdown: /tools/io-stablebaseline-sb/createproject.md
What createProject does on Stable Baseline
AI agents use createProject 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 | — | Optional emoji icon. Defaults to a folder emoji to match the UI. |
name | string | Yes | Project name. |
description | string | — | Optional description. |
workspace_id | string | Yes | Workspace UUID to create the project in. |
Parameters from the server's own tool schema.
Why createProject is rated Medium
An AI agent can call createProject 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 createProject 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 createProject, this is the rule to start with:
createProject 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 createProject call is checked against it from then on.
Questions about createProject
Create a new project inside a workspace. Mirrors the UI Create Project dialog. Auth: write on workspace + credential's can_lifecycle capability. Validates name (1..200) and description (0..2000); icon defaults to a folder emoji if omitted. The plan's project limit is checked on the server. Rate limit 30/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.
createProject accepts 4 parameters: icon, name, description, workspace_id. Required: name, workspace_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 createProject: 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.
createProject 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 createProject 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 createProject. 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.
createProject 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