Save the current profiler capture to a .prof file.
AI agents use save_profiler_capture 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.
Saving a profiler capture creates a new .prof file, modifying the filesystem in a reversible manner (the file can be deleted or overwritten). While this does have side effects (file creation), it is not destructive or irreversible in nature. The severity is medium rather than low because unintended profiler captures could fill disk space or expose performance data, but the impact is localized and recoverable.
From the tool's definition The tool description states it 'save[s] the current profiler capture to a .prof file', which creates a new file artifact. This is a write operation that persists data.
Documented attack patterns abuse exactly the kind of access save_profiler_capture gives an agent:
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_profiler_capture:
{
"version": "1",
"default": "deny",
"tools": {
"save_profiler_capture": {
"limits": [
{
"counter": "save_profiler_capture_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_profiler_capture 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.
Free to start. No card required.
Save the current profiler capture to a .prof file. 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.
Register the SK Wwise MCP server in PolicyLayer and add a rule for save_profiler_capture: 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.
save_profiler_capture is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_profiler_capture 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.
Set action: deny in the PolicyLayer policy for save_profiler_capture. 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.
save_profiler_capture 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.
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.