update_project_estimate_point · Plane MCP: Risk & Policy

WHAT IT DOES

What update_project_estimate_point does on Plane

AI agents use update_project_estimate_point 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 IT NEEDS A POLICY

Why update_project_estimate_point needs a policy

The tool performs an update operation on project estimate points, which is a reversible data modification typical of Write-category actions. While the empty description limits certainty, the naming convention and server context (project management) indicate this creates or modifies configuration data without executing code, deleting records, or handling financial transactions.

From the tool's definition Tool name 'update_project_estimate_point' indicates modification of project estimation data. The prefix 'update_' and context within Plane (a project management system) suggests creating or modifying reversible data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_project_estimate_point Rate-limited

update_project_estimate_point 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_project_estimate_point": {
      "limits": [
        {
          "counter": "update_project_estimate_point_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Plane, so you can run agents against it safely.

FAQ

Questions about update_project_estimate_point

What does the update_project_estimate_point tool do? +

update_project_estimate_point. 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.

How do I enforce a policy on update_project_estimate_point? +

Register the Plane MCP server in PolicyLayer and add a rule for update_project_estimate_point: 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.

What risk level is update_project_estimate_point? +

update_project_estimate_point is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_project_estimate_point? +

Yes. Add a rate_limit block to the update_project_estimate_point 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.

How do I block update_project_estimate_point completely? +

Set action: deny in the PolicyLayer policy for update_project_estimate_point. 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.

What MCP server provides update_project_estimate_point? +

update_project_estimate_point 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.