High Risk →

cli_migrate_project

cli_migrate_project

How to control cli_migrate_project ↓

What cli_migrate_project does on SK Wwise MCP

AI agents invoke cli_migrate_project to trigger actions in SK Wwise MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Why cli_migrate_project needs a policy

The name suggests a CLI operation that migrates a Wwise project, likely involving file system changes, format upgrades, or data transformations. Migration operations are typically irreversible (can't un-migrate a project) but also involve execution of external processes.

From the tool's definition Tool name 'cli_migrate_project' — description is empty and uninformative.

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

How to control cli_migrate_project

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_migrate_project:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cli_migrate_project": {
      "limits": [
        {
          "counter": "cli_migrate_project_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

cli_migrate_project stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about cli_migrate_project

What does the cli_migrate_project tool do? +

cli_migrate_project. It is categorised as a Execute tool in the SK Wwise MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cli_migrate_project? +

Register the SK Wwise MCP server in PolicyLayer and add a rule for cli_migrate_project: 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_migrate_project? +

cli_migrate_project is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit cli_migrate_project? +

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

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

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