AI agents use create_project_estimate 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 tool creates a new project estimate, which is a reversible write operation typical of project management systems. It modifies project data but does not execute arbitrary code, delete data permanently, or move money. Medium severity reflects that misconfigured estimates could affect project planning and resource allocation, though impacts are generally reversible.
From the tool's definition Tool name 'create_project_estimate' indicates creation of a new estimate resource. The 'create_' prefix combined with 'project_estimate' suggests data creation/modification. Description is empty, limiting precision.
Attacks that exploit this kind of access
create_project_estimate. 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: 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 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 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. 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 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 →