Get metadata about the currently open Wwise project, including project name, default language, and available platforms.
AI agents call get_wwise_project_info 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.
This tool queries and retrieves project metadata without creating, modifying, deleting, or executing any operations. It has no side effects and presents minimal risk even if misused by an AI agent, as it only returns informational data about the project configuration.
From the tool's definition Tool name and description indicate a retrieval operation: 'Get metadata about the currently open Wwise project, including project name, default language, and available platforms.' No modification, execution, or deletion is performed.
Documented attack patterns abuse exactly the kind of access get_wwise_project_info 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 get_wwise_project_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_wwise_project_info": {}
}
}get_wwise_project_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get metadata about the currently open Wwise project, including project name, default language, and available platforms. It is categorised as a Read tool in the SK Wwise MCP MCP Server, which means it retrieves data without modifying state.
Register the SK Wwise MCP server in PolicyLayer and add a rule for get_wwise_project_info: 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.
get_wwise_project_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_wwise_project_info 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 get_wwise_project_info. 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.
get_wwise_project_info 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.