Create a new tag with predefined color names (CRITICAL: use predefined color names, NOT hex colors)
AI agents use create_tag 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 new tag resource in Miro, which is a reversible write operation. Tags are metadata/organizational elements that can be updated or removed. There is no code execution, financial transaction, destructive deletion, or unauthorized data access.
From the tool's definition Tool name 'create_tag' and description indicating creation of a new tag with color specification. Creates data (a tag) that can be modified or deleted later.
Attacks that exploit this kind of access
Create a new tag with predefined color names (CRITICAL: use predefined color names, NOT hex colors). 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_tag: 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_tag 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_tag 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_tag. 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_tag 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 →