Create a new deck in a project, optionally in a specific space.
AI agents use codecks_create_deck to create or update resources in Codecks MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Codecks MCP Server environment.
This tool creates a new organizational structure (deck) within a project, which is a reversible write operation. It modifies project state by adding a new container but does not execute arbitrary code, delete data, or involve financial transactions. Severity is medium because creating unnecessary decks could clutter project organization, but the operation is easily undone by deletion.
From the tool's definition Tool name 'codecks_create_deck' and description 'Create a new deck in a project' indicate data creation. Decks are organizational containers in project management systems.
Attacks that exploit this kind of access
Create a new deck in a project, optionally in a specific space. It is categorised as a Write tool in the Codecks MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Codecks MCP Server MCP server in PolicyLayer and add a rule for codecks_create_deck: 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_create_deck is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the codecks_create_deck 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_create_deck. 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_create_deck 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 →