This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/deck-new.md
What deck_new does on UnClick
AI agents use deck_new to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
deck_count | number | — | Number of decks (default 1) |
Parameters from the server's own tool schema.
Why deck_new is rated Medium
The tool creates a new resource (a deck of cards), which is a Write operation. It has no financial, destructive, or execution implications. The blast radius is minimal — misuse would at worst create unwanted deck objects, making severity low.
From the tool's definition "Create and shuffle a new deck of cards"
Attacks that exploit this kind of access
The rule that runs deck_new 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_new, this is the rule to start with:
deck_new stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_new call is checked against it from then on.
Questions about deck_new
Create and shuffle a new deck of cards. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
deck_new accepts 1 parameter: deck_count. 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_new: 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_new 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 deck_new 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_new. 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_new 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