get_view_instances

THE RISK

Low Risk

Why get_view_instances needs a policy

This tool queries and returns information about currently open UI views in Wwise. It retrieves data about the application state with no side effects, no data modification, no code execution, and no destructive operations. This is a straightforward informational read operation with minimal risk even if misused by an agent.

From the tool's definition Tool name 'get_view_instances' with description 'Get all currently open view instances in the Wwise UI' indicates retrieval of UI state without modification.

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

POLICY

How to control get_view_instances

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_view_instances": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More SK Wwise MCP tools

Destructive delete_wwise_objects delete_wwise_objects Destructive destroy_wwise_transport Destroy a transport object, stopping any playback associated with it. Destructive remove_wwise_blend_assignment remove_wwise_blend_assignment Destructive remove_wwise_switch_assignments remove_wwise_switch_assignments Execute call_waapi Execute any WAAPI function with the given args and options. Execute cli_start_waapi_server cli_start_waapi_server Execute execute_command execute_command Execute execute_wwise_transport_action execute_wwise_transport_action

All 98 SK Wwise MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_view_instances

What does the get_view_instances tool do? +

Get all currently open view instances in the Wwise UI. 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_view_instances? +

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

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

Can I rate-limit get_view_instances? +

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

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

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

CHECK YOUR STACK →