List all cards from Codecks. Optionally filter by deck name, project, and/or status. Returns derivedStatus for each card.
AI agents call codecks_list_cards to retrieve information from Codecks MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists cards from a project management system with optional filtering. It performs no modifications, deletions, or external operations. It is a straightforward read operation that queries existing data.
From the tool's definition Tool name 'codecks_list_cards' and description 'List all cards from Codecks. Optionally filter by deck name, project, and/or status. Returns derivedStatus for each card.' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List all cards from Codecks. Optionally filter by deck name, project, and/or status. Returns derivedStatus for each card. It is categorised as a Read tool in the Codecks MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Codecks MCP Server MCP server in PolicyLayer and add a rule for codecks_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 Codecks MCP Server. Nothing to install.
codecks_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 codecks_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 codecks_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.
codecks_list_cards is provided by the Codecks MCP Server MCP server (microkorg/codecks-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 →