Create a new workspace (max 2 workspaces per user)
AI agents use create_workspace to create or update resources in Sidvy MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sidvy MCP Server environment.
This tool creates a new workspace, which is a data structure that can be created, modified, or deleted. It has no irreversible destructive effects, does not execute arbitrary code or external operations, and does not involve financial transactions. The blast radius is limited to the user's own workspace quota (max 2 per user) and affects only organizational data structures.
From the tool's definition Tool name 'create_workspace' and description 'Create a new workspace' directly indicate creation of new data structures with reversible effects (workspaces can be deleted or modified).
Attacks that exploit this kind of access
Create a new workspace (max 2 workspaces per user). It is categorised as a Write tool in the Sidvy MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sidvy MCP Server MCP server in PolicyLayer and add a rule for create_workspace: 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 Sidvy MCP Server. Nothing to install.
create_workspace 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 create_workspace 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 create_workspace. 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.
create_workspace is provided by the Sidvy MCP Server MCP server (martinhjartmyr/sidvy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →