execute_skill_script · Workflows MCP Server MCP

WHAT IT DOES

What execute_skill_script does on Workflows MCP Server

AI agents invoke execute_skill_script to trigger actions in Workflows MCP Server. 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.

WHY IT NEEDS A POLICY

Why execute_skill_script needs a policy

This tool executes Python scripts whose behavior depends entirely on the script content (an argument controlled by the AI agent). Python script execution is inherently an Execute operation with high blast radius—it can read files, modify system state, make network calls, and trigger side effects. While the tool description is empty, the server context makes the execution semantics clear.

From the tool's definition Tool name 'execute_skill_script' combined with server description stating it 'programmatically create, manage, and execute independent Python workflow scripts' indicates this tool runs arbitrary Python code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_skill_script Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_skill_script": {
      "limits": [
        {
          "counter": "execute_skill_script_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Workflows MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_skill_script

What does the execute_skill_script tool do? +

execute_skill_script. It is categorised as a Execute tool in the Workflows MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_skill_script? +

Register the Workflows MCP Server MCP server in PolicyLayer and add a rule for execute_skill_script: 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 Workflows MCP Server. Nothing to install.

What risk level is execute_skill_script? +

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

Can I rate-limit execute_skill_script? +

Yes. Add a rate_limit block to the execute_skill_script 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 execute_skill_script completely? +

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

execute_skill_script is provided by the Workflows MCP Server MCP server (livus-ai/skills-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.