List cards of a project filtered by type, status, sprint, developer, or year
AI agents call list_cards 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.
The tool performs data retrieval with optional filtering, which is a read-only operation with no side effects. It does not create, modify, delete, or execute any operations. Severity is low because listing cards poses minimal risk even if misused by an AI agent.
From the tool's definition list_cards retrieves and queries card data with filter parameters (type, status, sprint, developer, year); no modification, deletion, or execution occurs.
Attacks that exploit this kind of access
List cards of a project filtered by type, status, sprint, developer, or year. 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_cards: 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_cards 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_cards 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_cards. 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_cards 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 →