Create a workspace for the authenticated account.
AI agents use staticx_create_workspace to create or update resources in StaticX MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your StaticX MCP Server environment.
The tool creates a new workspace resource, which is a reversible write operation. It modifies account state by adding a new workspace, but the action can be undone (workspace can be deleted). This is not destructive (irreversible), not financial, and not read-only.
From the tool's definition Tool name includes 'create' and description states 'Create a workspace for the authenticated account.' This is a data creation operation.
Attacks that exploit this kind of access
Create a workspace for the authenticated account. It is categorised as a Write tool in the StaticX MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the StaticX MCP Server MCP server in PolicyLayer and add a rule for staticx_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 StaticX MCP Server. Nothing to install.
staticx_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 staticx_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 staticx_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.
staticx_create_workspace is provided by the StaticX MCP Server MCP server (madprodworks-coder/staticx-mcp-server). 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 →