vibecontrols_workspace_create

SERVERVibecontrols SOURCE@vibecontrols/mcp

Medium RISK CLASS

Category Write

Parameters 41 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/vibecontrols-mcp/vibecontrols-workspace-create.md

WHAT IT DOES

What vibecontrols_workspace_create does on Vibecontrols

AI agents use vibecontrols_workspace_create to create or update resources in Vibecontrols, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vibecontrols environment.

Parameter	Type	Required	Description
`name`	string	Yes	Workspace name
`slug`	string	—	URL slug (auto-derived from name as kebab-case when omitted)
`description`	string	—	Workspace description
`organizationId`	string	—	Owning organization id (defaults to the actor's organization from the access token)

Parameters from the server's own tool schema.

RISK

Why vibecontrols_workspace_create is rated Medium

An AI agent can call vibecontrols_workspace_create faster than any human can review: one bad instruction and it creates or modifies resources in Vibecontrols by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vibecontrols_workspace_create safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Vibecontrols, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vibecontrols_workspace_create, this is the rule to start with:

vibecontrols_workspace_create Rate-limited

vibecontrols_workspace_create 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vibecontrols_workspace_create": {
      "limits": [
        {
          "counter": "vibecontrols_workspace_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vibecontrols, apply this rule, and every vibecontrols_workspace_create call is checked against it from then on.

FAQ

Questions about vibecontrols_workspace_create

What does the vibecontrols_workspace_create tool do? +

Create a workspace (global layer). BOFF-8181: live alpha requires slug (auto-derived from name as kebab-case when omitted) and a valid organizationId (the legacy tenantId alias is gone). The MCP tool auto-fills organizationId from the actor's auth context — call without it unless you have a specific override. It is categorised as a Write tool in the Vibecontrols MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does vibecontrols_workspace_create accept? +

vibecontrols_workspace_create accepts 4 parameters: name, slug, description, organizationId. Required: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on vibecontrols_workspace_create? +

Register the Vibecontrols MCP server in PolicyLayer and add a rule for vibecontrols_workspace_create: 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 Vibecontrols. Nothing to install.

What risk level is vibecontrols_workspace_create? +

vibecontrols_workspace_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit vibecontrols_workspace_create? +

Yes. Add a rate_limit block to the vibecontrols_workspace_create 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.

How do I block vibecontrols_workspace_create completely? +

Set action: deny in the PolicyLayer policy for vibecontrols_workspace_create. 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.

What MCP server provides vibecontrols_workspace_create? +

vibecontrols_workspace_create is provided by the Vibecontrols MCP server (@vibecontrols/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vibecontrols, and thousands of servers like it.

This server

All 672 Vibecontrols tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →