AI agents call list_project_estimate_points to retrieve information from Plane without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the naming convention strongly suggests this tool queries or retrieves estimate point information associated with a project. This is a read operation with no side effects—it retrieves data without creating, modifying, deleting, or executing external operations. The blast radius of misuse is minimal, limited to potential information disclosure.
From the tool's definition Tool name 'list_project_estimate_points' indicates retrieval of estimate point data. The 'list_' prefix is a standard pattern for read-only query operations that return collections of data without modification.
Attacks that exploit this kind of access
list_project_estimate_points. It is categorised as a Read tool in the Plane MCP Server, which means it retrieves data without modifying state.
Register the Plane MCP server in PolicyLayer and add a rule for list_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.
list_project_estimate_points is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_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 list_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.
list_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 →