Group multiple existing items together
AI agents use create_group to create or update resources in Miro MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Miro MCP Server environment.
This tool modifies the structure and organization of existing items by grouping them, which is a Write operation. It is reversible (groups can be ungrouped) and does not create, delete, or irreversibly alter data. The severity is medium because grouping operations on collaborative boards could affect visibility and workflow for other users, but the impact is non-destructive and can be undone.
From the tool's definition Tool name 'create_group' and description 'Group multiple existing items together' indicates a reversible modification operation that organizes existing board content without creating new items or deleting data.
Attacks that exploit this kind of access
Group multiple existing items together. It is categorised as a Write tool in the Miro MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Miro MCP Server MCP server in PolicyLayer and add a rule for create_group: 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 Miro MCP Server. Nothing to install.
create_group 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_group 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_group. 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_group is provided by the Miro MCP Server MCP server (soul-script/miro-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 →