AI agents call list_initiatives 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.
List operations retrieve and enumerate data without side effects. The absence of a description is noted, but the verb 'list' has strong semantic association with retrieval-only operations. Given the sibling tools include both Read operations (count_work_items) and Write operations (create_cycle, create_initiative), this tool's naming convention aligns with Read.
From the tool's definition Tool name 'list_initiatives' indicates a retrieval operation that queries and returns a list of initiatives. The 'list' prefix is characteristic of Read operations that fetch data without modification.
Attacks that exploit this kind of access
list_initiatives. 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_initiatives: 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_initiatives 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_initiatives 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_initiatives. 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_initiatives 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 →