Create a frame container to organize other items
AI agents use create_frame 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 creates a frame—a reversible, non-destructive modification to board content. It adds a new organizational container without executing code, deleting data, or causing financial impact. The action is easily undoable (frame can be deleted), making it a Write operation with low severity appropriate for collaborative board management.
From the tool's definition Tool name 'create_frame' and description 'Create a frame container to organize other items' indicate creation of a new collaborative artifact on a Miro board.
Attacks that exploit this kind of access
Create a frame container to organize other items. 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_frame: 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_frame 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_frame 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_frame. 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_frame 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 →