remove_wwise_blend_assignment

THE RISK

Critical Risk

Why remove_wwise_blend_assignment needs a policy

The 'remove_' prefix strongly implies deletion or irreversible removal of a blend assignment configuration in a Wwise project. Its sibling 'add_wwise_blend_assignment' is the complementary creation operation. Removing project configuration data is typically a destructive action. Empty description lowers confidence, but naming convention and context support Destructive classification.

From the tool's definition Tool name 'remove_wwise_blend_assignment' and sibling tool 'add_wwise_blend_assignment' suggest this removes a blend assignment from a Wwise project. The description is empty, lowering confidence.

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

POLICY

How to control remove_wwise_blend_assignment

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_wwise_blend_assignment"
  ]
}

remove_wwise_blend_assignment disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More SK Wwise MCP tools

Destructive delete_wwise_objects delete_wwise_objects Destructive destroy_wwise_transport Destroy a transport object, stopping any playback associated with it. Destructive remove_wwise_switch_assignments remove_wwise_switch_assignments Execute call_waapi Execute any WAAPI function with the given args and options. Execute cli_start_waapi_server cli_start_waapi_server Execute execute_command execute_command Execute execute_wwise_transport_action execute_wwise_transport_action Execute start_profiler_capture Start profiler capture and return the capture start time. No arguments required.

All 98 SK Wwise MCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in SK Wwise MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about remove_wwise_blend_assignment

What does the remove_wwise_blend_assignment tool do? +

remove_wwise_blend_assignment. It is categorised as a Destructive tool in the SK Wwise MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_wwise_blend_assignment? +

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

remove_wwise_blend_assignment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_wwise_blend_assignment? +

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

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

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

CHECK YOUR STACK →