set_shuffle

Enable/disable shuffle and set repeat mode (off, one, all).

SERVERIconnect SOURCEiconnect-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/set-shuffle.md

WHAT IT DOES

What set_shuffle does on Iconnect

AI agents use set_shuffle to create or update resources in Iconnect, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iconnect environment.

RISK

Why set_shuffle is rated Medium

This tool modifies playback settings (shuffle and repeat mode) in a media player. It creates or modifies state reversibly — settings can always be toggled back. No data is deleted, no code is executed, and no financial transactions occur. Severity is low since the blast radius of misconfiguring playback settings is minimal.

From the tool's definition Enable/disable shuffle and set repeat mode (off, one, all)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_shuffle safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_shuffle, this is the rule to start with:

set_shuffle Rate-limited

set_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": {
    "set_shuffle": {
      "limits": [
        {
          "counter": "set_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 Iconnect, apply this rule, and every set_shuffle call is checked against it from then on.

FAQ

Questions about set_shuffle

What does the set_shuffle tool do? +

Enable/disable shuffle and set repeat mode (off, one, all). It is categorised as a Write tool in the Iconnect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_shuffle? +

Register the Iconnect MCP server in PolicyLayer and add a rule for set_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 Iconnect. Nothing to install.

What risk level is set_shuffle? +

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

Can I rate-limit set_shuffle? +

Yes. Add a rate_limit block to the set_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 set_shuffle completely? +

Set action: deny in the PolicyLayer policy for set_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 set_shuffle? +

set_shuffle is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools →

Across the catalogue

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

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