AI agents call set_profiler_cursor as a supporting operation in SK Wwise MCP workflows.
The tool name suggests it moves a cursor within a profiler timeline/view, which is likely a UI/navigation action with no significant data modification or destructive effects. However, with no description available, confidence is low. Based on context of a Wwise profiling tool, this most likely adjusts a playback or analysis cursor position, falling into Other or Read category with low severity.
From the tool's definition Tool name is 'set_profiler_cursor'; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access set_profiler_cursor 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 set_profiler_cursor:
{
"version": "1",
"default": "deny",
"tools": {
"set_profiler_cursor": {
"limits": [
{
"counter": "set_profiler_cursor_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} set_profiler_cursor gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
set_profiler_cursor. It is categorised as a Other tool in the SK Wwise MCP MCP Server, which means it performs auxiliary operations.
Register the SK Wwise MCP server in PolicyLayer and add a rule for set_profiler_cursor: 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.
set_profiler_cursor is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the set_profiler_cursor 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 set_profiler_cursor. 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.
set_profiler_cursor 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.