superskills_invoke
AI agents invoke superskills_invoke to trigger actions in Superskills. 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.
An 'invoke' operation on a CLI skill gateway most likely triggers execution of external commands or scripts with effects determined by arguments. This is Execute category due to potential for running arbitrary code or shell commands. High severity because such invocations could have wide-ranging side effects depending on which skills are exposed and what arguments an AI agent supplies.
From the tool's definition Tool name 'superskills_invoke' combined with server description stating it 'exposes your local CLI skills to any AI assistant' indicates invocation of local commands or scripts. Sibling tool 'superskills_run' reinforces this pattern.
Attacks that exploit this kind of access
superskills_invoke. It is categorised as a Execute tool in the Superskills MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Superskills MCP server in PolicyLayer and add a rule for superskills_invoke: 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 Superskills. Nothing to install.
superskills_invoke 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 superskills_invoke 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 superskills_invoke. 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.
superskills_invoke is provided by the Superskills MCP server (lee2026-dev/superskills-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →