AI agents invoke convert_audio_to_wav 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.
The tool name suggests it converts audio files to WAV format, which is an execution/transformation operation. However, the description is empty, lowering confidence. Based on the name alone, this appears to be an Execute category tool as it runs a conversion process. Severity is medium as it could overwrite files during conversion. Confidence is low due to the empty description.
From the tool's definition Tool name 'convert_audio_to_wav' and empty description. The name implies audio file conversion processing.
Documented attack patterns abuse exactly the kind of access convert_audio_to_wav 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 convert_audio_to_wav:
{
"version": "1",
"default": "deny",
"tools": {
"convert_audio_to_wav": {
"limits": [
{
"counter": "convert_audio_to_wav_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} convert_audio_to_wav 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.
convert_audio_to_wav. 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 convert_audio_to_wav: 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.
convert_audio_to_wav 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 convert_audio_to_wav 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 convert_audio_to_wav. 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.
convert_audio_to_wav 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.