delete_wwise_objects

THE RISK

Critical Risk

Why delete_wwise_objects needs a policy

Deletion of Wwise objects cannot be undone and destroys audio project assets. This is a Destructive action by definition, not merely a Write operation. High severity reflects the risk that an AI agent could remove important audio objects, voices, switches, or blends from a production Wwise project without recovery. Confidence is high despite empty description because 'delete' is an unequivocal destructive operation.

From the tool's definition Tool name is 'delete_wwise_objects' — the verb 'delete' explicitly indicates irreversible removal of data. Description is empty, but the name alone is unambiguous.

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

POLICY

How to control delete_wwise_objects

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

policy.json

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

delete_wwise_objects 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 destroy_wwise_transport Destroy a transport object, stopping any playback associated with it. Destructive remove_wwise_blend_assignment remove_wwise_blend_assignment 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 delete_wwise_objects

What does the delete_wwise_objects tool do? +

delete_wwise_objects. 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 delete_wwise_objects? +

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

delete_wwise_objects 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 delete_wwise_objects? +

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

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

delete_wwise_objects 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 →