deck_shuffle

Reshuffle an existing deck.

SERVERUnClick SOURCE@unclick/mcp-server

Medium RISK CLASS

Category Write

Parameters 11 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/deck-shuffle.md

WHAT IT DOES

What deck_shuffle does on UnClick

AI agents use deck_shuffle 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_id`	string	Yes	Deck ID to reshuffle

Parameters from the server's own tool schema.

RISK

Why deck_shuffle is rated Medium

Reshuffling modifies the state of an existing deck (reorders its contents), which is a reversible data modification. No data is deleted, no code is executed, and there are no financial implications. Severity is low as the blast radius of misuse is minimal — at worst, a deck is reordered unexpectedly.

From the tool's definition Reshuffle an existing deck

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs deck_shuffle 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_shuffle, this is the rule to start with:

deck_shuffle Rate-limited

deck_shuffle 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deck_shuffle": {
      "limits": [
        {
          "counter": "deck_shuffle_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every deck_shuffle call is checked against it from then on.

FAQ

Questions about deck_shuffle

What does the deck_shuffle tool do? +

Reshuffle an existing deck. 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.

What parameters does deck_shuffle accept? +

deck_shuffle accepts 1 parameter: deck_id. Required: deck_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on deck_shuffle? +

Register the UnClick MCP server in PolicyLayer and add a rule for deck_shuffle: 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.

What risk level is deck_shuffle? +

deck_shuffle is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit deck_shuffle? +

Yes. Add a rate_limit block to the deck_shuffle 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.

How do I block deck_shuffle completely? +

Set action: deny in the PolicyLayer policy for deck_shuffle. 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.

What MCP server provides deck_shuffle? +

deck_shuffle 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.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →