Medium Risk

cli_move_media_ids

cli_move_media_ids

How to control cli_move_media_ids ↓

What cli_move_media_ids does on SK Wwise MCP

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

Medium Risk

Why cli_move_media_ids needs a policy

The tool name suggests it relocates or reorganizes media IDs within a Wwise project—a reversible data modification operation typical of Write category. Moving media IDs likely restructures project assets but does not permanently delete them. Context from sibling CLI migration and project tools supports this as a project mutation tool.

From the tool's definition Tool name 'cli_move_media_ids' indicates modification of media resource organization; sibling tools include 'cli_convert_external_sources', 'cli_create_new_project', and 'cli_migrate_project' which are Write operations in a Wwise project context.

Documented attack patterns abuse exactly the kind of access cli_move_media_ids gives an agent:

How to control cli_move_media_ids

PolicyLayer is an MCP gateway — it sits between your AI agents and SK Wwise MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for cli_move_media_ids:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cli_move_media_ids": {
      "limits": [
        {
          "counter": "cli_move_media_ids_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register SK Wwise MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about cli_move_media_ids

What does the cli_move_media_ids tool do? +

cli_move_media_ids. It is categorised as a Write tool in the SK Wwise MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cli_move_media_ids? +

Register the SK Wwise MCP server in PolicyLayer and add a rule for cli_move_media_ids: 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 SK Wwise MCP. Nothing to install.

What risk level is cli_move_media_ids? +

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

Can I rate-limit cli_move_media_ids? +

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

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

cli_move_media_ids is provided by the SK Wwise MCP server (silver-rain-dev/sk-wwise-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SK Wwise MCP tool call.

Start from SK Wwise MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

98 SK Wwise MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.