AI agents use create_project_estimate_points 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.
The 'create' verb and context of project/work item management tools indicate this creates or modifies project metadata (estimate points). This is a Write operation because it produces reversible changes to project data. Severity is medium because misuse could corrupt project planning data but lacks the irreversibility of Destructive operations or financial impact.
From the tool's definition Tool name 'create_project_estimate_points' indicates creation of estimate points; description is empty but sibling tools like 'create_cycle', 'create_label', 'create_milestone', 'create_module' establish a pattern of Write operations on Plane work management…
Attacks that exploit this kind of access
create_project_estimate_points. 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_project_estimate_points: 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_project_estimate_points 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_project_estimate_points 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_project_estimate_points. 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_project_estimate_points is provided by the Plane MCP server (@makeplane/plane-mcp-server). 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 →