Stop profiler capture and return the capture end time. No arguments required.
AI agents invoke stop_profiler_capture 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.
Stopping a profiler capture is an Execute action because it triggers an operation with external effects on the Wwise profiler state, rather than merely reading data or writing persistent data. However, it is not Destructive because the action is reversible (a new capture can be started).
From the tool's definition The tool stops an active profiler capture session, which triggers a state change in the Wwise profiler and returns data. This is an operational action that affects the running state of an external system (Wwise Authoring API).
Documented attack patterns abuse exactly the kind of access stop_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 stop_profiler_capture:
{
"version": "1",
"default": "deny",
"tools": {
"stop_profiler_capture": {
"limits": [
{
"counter": "stop_profiler_capture_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_profiler_capture 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.
Free to start. No card required.
Stop profiler capture and return the capture end time. No arguments required. 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.
Register the SK Wwise MCP server in PolicyLayer and add a rule for stop_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.
stop_profiler_capture is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the stop_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 stop_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.
stop_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.