List all developers (dev_XXX IDs). Call this BEFORE assigning developers to cards. Optional: projectId to filter by project team.
AI agents call list_developers to retrieve information from Planning Game without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries developer information without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that returns a list of developers, making it a Read category tool with low severity due to minimal blast radius if misused by an agent.
From the tool's definition Tool name 'list_developers' and description explicitly states it 'List all developers', which is a retrieval operation with no side effects. The optional projectId parameter is used for filtering, not modification.
Attacks that exploit this kind of access
List all developers (dev_XXX IDs). Call this BEFORE assigning developers to cards. Optional: projectId to filter by project team. It is categorised as a Read tool in the Planning Game MCP Server, which means it retrieves data without modifying state.
Register the Planning Game MCP server in PolicyLayer and add a rule for list_developers: 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 Planning Game. Nothing to install.
list_developers 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_developers 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_developers. 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_developers is provided by the Planning Game MCP server (planning-game-mcp). 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 →