This record as markdown: /tools/cmet7-plane-mcp/create-state.md
What create_state does on Plane
AI agents use create_state 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_state is rated Medium
Creating a workflow state is a reversible write operation that configures project management settings. It has no direct destructive impact, does not execute arbitrary code, and does not involve financial transactions. The blast radius is minimal as workflow states are metadata configurations that can be edited or removed by other tools. Severity is low because the impact is limited to project configuration scope.
From the tool's definition Tool name 'create_state' and description 'Create a new workflow state in a project' indicate creation of new configuration data. This is a reversible write operation that adds a workflow state without deleting or modifying existing data.
Attacks that exploit this kind of access
The rule that runs create_state 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_state, this is the rule to start with:
create_state 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_state call is checked against it from then on.
Questions about create_state
Create a new workflow state 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_state: 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_state 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_state 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_state. 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_state 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