AI agents call get_profiler_rtpcs 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 retrieves profiler data (RTPCs) from a Wwise project. RTPCs are runtime parameters used for audio control and profiling. Retrieval of profiler metrics and configuration data constitutes a Read operation with no side effects.
From the tool's definition Tool name 'get_profiler_rtpcs' indicates retrieval of profiler Real-Time Parameter Controls (RTPCs) from Wwise. The 'get_' prefix and 'profiler' context suggest data querying without modification.
Documented attack patterns abuse exactly the kind of access get_profiler_rtpcs 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_profiler_rtpcs:
{
"version": "1",
"default": "deny",
"tools": {
"get_profiler_rtpcs": {}
}
}get_profiler_rtpcs 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_profiler_rtpcs. 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_profiler_rtpcs: 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_profiler_rtpcs 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_profiler_rtpcs 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_profiler_rtpcs. 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_profiler_rtpcs 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.