AI agents invoke cli_verify_project to trigger actions in SK Wwise MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Based on the naming convention of sibling tools (cli_convert_external_sources, cli_create_new_project, cli_migrate_project), this appears to be a CLI command that runs a verification/validation process on a Wwise project. This would be an Execute-category action as it triggers an external operation. However, the empty description significantly lowers confidence.
From the tool's definition Tool name 'cli_verify_project' and server context of Wwise CLI operations; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access cli_verify_project 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 cli_verify_project:
{
"version": "1",
"default": "deny",
"tools": {
"cli_verify_project": {
"limits": [
{
"counter": "cli_verify_project_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}cli_verify_project stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
cli_verify_project. It is categorised as a Execute tool in the SK Wwise MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SK Wwise MCP server in PolicyLayer and add a rule for cli_verify_project: 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.
cli_verify_project is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cli_verify_project 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 cli_verify_project. 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.
cli_verify_project 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.