superskills_run
AI agents invoke superskills_run 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.
This tool appears designed to execute code or commands on the local system. While the empty description limits confidence slightly, the tool name 'run' paired with a 'general-purpose MCP gateway' for 'local CLI skills' indicates arbitrary code execution capability.
From the tool's definition Tool name 'superskills_run' combined with server purpose ('exposes your local CLI skills to any AI assistant') and the presence of sibling tools like 'superskills_invoke' strongly suggest execution of arbitrary CLI commands or local scripts.
Attacks that exploit this kind of access
superskills_run. 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_run: 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_run 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_run 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_run. 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_run 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 →