AI agents call plane-member-list 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.
This tool retrieves project membership information without modifying, deleting, or executing any operations. It is a straightforward read operation that queries and returns data about project members.
From the tool's definition Tool name 'plane-member-list' and description 'List all members of a project' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List all members of a project. 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 plane-member-list: 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.
plane-member-list 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 plane-member-list 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 plane-member-list. 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.
plane-member-list is provided by the Plane MCP server (philipvanlewis/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 →