This record as markdown: /tools/cmet7-plane-mcp/create-label.md
What create_label does on Plane
AI agents use create_label to create or update resources in Plane, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Plane environment.
Why create_label is rated Medium
Creating a label is a reversible write operation—labels can be modified, deleted, or reassigned. It does not execute code, delete data irreversibly, or impact financial systems. The severity is medium rather than low because careless label creation could disrupt project organization and workflows if an agent creates many labels or uses inappropriate names, affecting team collaboration.
From the tool's definition Tool creates a new label in a project. The name 'create_label' and description 'Create a new label in a project' directly indicate a create operation that adds data.
Attacks that exploit this kind of access
The rule that runs create_label safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_label, this is the rule to start with:
create_label stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Plane, apply this rule, and every create_label call is checked against it from then on.
Questions about create_label
Create a new label in a project. It is categorised as a Write tool in the Plane MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Plane MCP server in PolicyLayer and add a rule for create_label: 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 Plane. Nothing to install.
create_label 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_label 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_label. 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_label is provided by the Plane MCP server (cmet7/plane-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Plane, and thousands of servers like it.
This server
Across the catalogue