Disconnect Wwise from a connected remote Sound Engine instance. No arguments required.
AI agents invoke disconnect_from_remote 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 executes an action against an external system (a remote Sound Engine instance) by severing its connection. It's not simply reading or writing data, nor is it destructive or financial. It triggers an external operational state change (disconnection), making Execute the most appropriate category. Misuse could interrupt an active audio session or profiling session, causing medium-level disruption.
From the tool's definition 'Disconnect Wwise from a connected remote Sound Engine instance' — triggers an external operation that terminates an active remote connection
Documented attack patterns abuse exactly the kind of access disconnect_from_remote 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 disconnect_from_remote:
{
"version": "1",
"default": "deny",
"tools": {
"disconnect_from_remote": {
"limits": [
{
"counter": "disconnect_from_remote_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}disconnect_from_remote 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.
Disconnect Wwise from a connected remote Sound Engine instance. 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 disconnect_from_remote: 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.
disconnect_from_remote 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 disconnect_from_remote 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 disconnect_from_remote. 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.
disconnect_from_remote 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.