This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/deck-draw.md
What deck_draw does on UnClick
AI agents call deck_draw to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
count | number | — | Number of cards to draw (default 1) |
deck_id | string | Yes | Deck ID from deck_new |
Parameters from the server's own tool schema.
Why deck_draw is rated Low
Drawing a card is fundamentally a read operation that retrieves data about card contents. While it may advance game state in some contexts, the tool itself performs no write, deletion, or execution of external commands—it simply returns card information. The low severity reflects that misuse has no real-world consequences (e.g., no financial loss, data destruction, or code execution).
From the tool's definition Tool name 'deck_draw' and description 'Draw cards from a deck' indicate a retrieval operation that queries or fetches data (card values) from a game deck without modifying or deleting the deck state.
Attacks that exploit this kind of access
The rule that runs deck_draw safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deck_draw, this is the rule to start with:
deck_draw is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every deck_draw call is checked against it from then on.
Questions about deck_draw
Draw cards from a deck. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
deck_draw accepts 2 parameters: count, deck_id. Required: deck_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for deck_draw: 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 UnClick. Nothing to install.
deck_draw 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 deck_draw 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 deck_draw. 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.
deck_draw is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue