High Risk →

mcx_run_skill

Run a registered MCX skill by name. Available skills: [${skillNames}] ${skillList}

How to control mcx_run_skill ↓

AI agents invoke mcx_run_skill to trigger actions in MCX (Modular Code Execution). 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.

High Risk

mcx_run_skill triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Documented attack patterns abuse exactly the kind of access mcx_run_skill gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MCX (Modular Code Execution), and nothing reaches the server without passing your rules. This is the rule we recommend for mcx_run_skill:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "mcx_run_skill": {
      "limits": [
        {
          "counter": "mcx_run_skill_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

mcx_run_skill 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.

  1. Create a free account and register MCX (Modular Code Execution) — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the mcx_run_skill tool do? +

Run a registered MCX skill by name. Available skills: [${skillNames}] ${skillList}. It is categorised as a Execute tool in the MCX (Modular Code Execution) MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on mcx_run_skill? +

Register the MCX (Modular Code Execution) MCP server in PolicyLayer and add a rule for mcx_run_skill: 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 MCX (Modular Code Execution). Nothing to install.

What risk level is mcx_run_skill? +

mcx_run_skill is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit mcx_run_skill? +

Yes. Add a rate_limit block to the mcx_run_skill 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.

How do I block mcx_run_skill completely? +

Set action: deny in the PolicyLayer policy for mcx_run_skill. 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.

What MCP server provides mcx_run_skill? +

mcx_run_skill is provided by the MCX (Modular Code Execution) MCP server (schizoidcock/mcx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCX (Modular Code Execution) tool call.

Deterministic rules across all 18 MCX (Modular Code Execution) tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

18 MCX (Modular Code Execution) tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.