AI agents use spaces_create to create or update resources in Musubix — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Musubix environment.
This tool creates a new Copilot Space with associated metadata and context management. Creation is reversible (spaces can typically be deleted), making it a Write operation rather than Execute or Destructive. The blast radius is medium because unintended space creation could clutter resources and potentially expose context inappropriately, but the action itself is not irreversible or code-executing.
From the tool's definition Tool name 'spaces_create' and description stating '新しいCopilot Spaceを作成します' (creates a new Copilot Space) indicate creation of a new resource.
Attacks that exploit this kind of access
新しいCopilot Spaceを作成します。要件、設計、タスク、ファイルを関連付けて、コンテキストを管理できます。. It is categorised as a Write tool in the Musubix MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Musubix MCP server in PolicyLayer and add a rule for spaces_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 Musubix. Nothing to install.
spaces_create 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 spaces_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.
Set action: deny in the PolicyLayer policy for spaces_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.
spaces_create is provided by the Musubix MCP server (@nahisaho/musubix-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 →