Low Risk

get_layout_names

Get all available Wwise UI layout names.

How to control get_layout_names ↓

What get_layout_names does on SK Wwise MCP

AI agents call get_layout_names 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_layout_names needs a policy

This tool queries and returns a list of available UI layout names from Wwise. It is a read-only operation that retrieves metadata about the application's UI configuration without creating, modifying, or deleting any data. The verb 'get' and the passive nature of retrieving layout names confirm this is a Read category tool with minimal risk.

From the tool's definition Tool name 'get_layout_names' and description 'Get all available Wwise UI layout names' indicate retrieval of configuration/UI state data with no modification or side effects.

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

How to control get_layout_names

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

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

get_layout_names 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_layout_names

What does the get_layout_names tool do? +

Get all available Wwise UI layout names. 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_layout_names? +

Register the SK Wwise MCP server in PolicyLayer and add a rule for get_layout_names: 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_layout_names? +

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

Can I rate-limit get_layout_names? +

Yes. Add a rate_limit block to the get_layout_names 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_layout_names completely? +

Set action: deny in the PolicyLayer policy for get_layout_names. 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_layout_names? +

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