Start profiler capture and return the capture start time. No arguments required.
AI agents invoke start_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.
This tool triggers an external operation (profiling) within the Wwise audio engine, which is a runtime side effect that cannot be undone by simply calling another tool—profiling data collection has started and will continue until stopped. While not destructive or financial, it modifies the runtime state of the Wwise application.
From the tool's definition Tool name 'start_profiler_capture' and description 'Start profiler capture' indicate an action that initiates an external operation (profiler capture) whose effects depend on the Wwise project state and subsequent actions.
Documented attack patterns abuse exactly the kind of access start_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 start_profiler_capture:
{
"version": "1",
"default": "deny",
"tools": {
"start_profiler_capture": {
"limits": [
{
"counter": "start_profiler_capture_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}start_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.
Start profiler capture and return the capture start 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 start_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.
start_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 start_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 start_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.
start_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.