Low Risk

get_commands

Get the list of all available UI commands in Wwise.

How to control get_commands ↓

What get_commands does on SK Wwise MCP

AI agents call get_commands to retrieve information from SK Wwise MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_commands needs a policy

This tool retrieves and lists available UI commands from Wwise, similar to a help or documentation query. It has no side effects—it does not execute commands, modify data, or trigger actions. This is a straightforward Read operation with minimal security risk.

From the tool's definition Tool name 'get_commands' and description 'Get the list of all available UI commands in Wwise' indicate a query/retrieval operation that returns information about available commands without modifying state or executing them.

Documented attack patterns abuse exactly the kind of access get_commands gives an agent:

How to control get_commands

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 get_commands:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_commands": {}
  }
}

get_commands is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register SK Wwise MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_commands

What does the get_commands tool do? +

Get the list of all available UI commands in Wwise. It is categorised as a Read tool in the SK Wwise MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_commands? +

Register the SK Wwise MCP server in PolicyLayer and add a rule for get_commands: 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.

What risk level is get_commands? +

get_commands is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_commands? +

Yes. Add a rate_limit block to the get_commands 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.

How do I block get_commands completely? +

Set action: deny in the PolicyLayer policy for get_commands. 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.

What MCP server provides get_commands? +

get_commands 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.

Enforce policy on every SK Wwise MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.