AI agents invoke skill_execute to trigger actions in Musubix. 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 runs skills with user-supplied parameters and returns results, making it a classic Execute category tool. The severity is high because skill execution could have broad side effects depending on what skills are available and what parameters are passed; without knowing the skill catalog, an AI agent could potentially trigger unintended operations.
From the tool's definition Tool name 'skill_execute' combined with description stating it 'executes (実行します) the specified skill' and 'returns results.' The Japanese description explicitly uses 実行 (execute/run), indicating the tool triggers external operations whose effects depend on…
Attacks that exploit this kind of access
指定したスキルを実行します。 スキルのパラメータを指定して実行し、結果を返します。. It is categorised as a Execute tool in the Musubix MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Musubix MCP server in PolicyLayer and add a rule for skill_execute: 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 Musubix. Nothing to install.
skill_execute 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 skill_execute 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 skill_execute. 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.
skill_execute is provided by the Musubix MCP server (@nahisaho/musubix-mcp-server). 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 →