Medium Risk

save_wwise_project

Save the current Wwise project.

How to control save_wwise_project ↓

What save_wwise_project does on SK Wwise MCP

AI agents use save_wwise_project 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 save_wwise_project needs a policy

This tool creates or modifies data reversibly by persisting the current project state. It is a Write operation rather than Destructive because saving is non-destructive and reversible (prior versions could theoretically be recovered, and the operation itself does not delete data).

From the tool's definition save_wwise_project: The tool explicitly performs a save operation on the current Wwise project, modifying its persistent state on disk.

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

How to control save_wwise_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 save_wwise_project:

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

save_wwise_project 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 save_wwise_project

What does the save_wwise_project tool do? +

Save the current Wwise project. 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 save_wwise_project? +

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

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

Can I rate-limit save_wwise_project? +

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

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

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