List all decks in a project with card counts and space info. Uses default project if not specified.
AI agents call codecks_list_decks 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 queries and returns information about decks within a project—a read-only operation with no side effects, no data modification, and no execution of external operations. It poses minimal security risk when misused by an AI agent, as the worst case is retrieving organizational information about the project structure.
From the tool's definition Tool name 'codecks_list_decks' and description 'List all decks in a project' clearly indicate a retrieval/query operation with no modification of data. The phrase 'with card counts and space info' confirms it returns information only.
Attacks that exploit this kind of access
List all decks in a project with card counts and space info. Uses default project if not specified. 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_decks: 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_decks 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_decks 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_decks. 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_decks 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 →