AI agents invoke skills_run_script to trigger actions in Skills. 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.
A 'run_script' tool executes arbitrary or parameterized scripts, which falls squarely into the Execute category. The effect depends entirely on what script is provided as an argument—it could modify state, trigger external operations, or cause side effects. Without explicit constraints limiting it to read-only operations, this poses a high risk if an AI agent calls it with malicious or unintended script content.
From the tool's definition Tool name 'skills_run_script' directly indicates script execution. Sibling tools like 'skills_find_relevant', 'skills_get_asset', 'skills_get_body', 'skills_get_options', 'skills_get_reference', and 'skills_list_all' are all Read operations (search, retrieve,…
Attacks that exploit this kind of access
skills_run_script. It is categorised as a Execute tool in the Skills MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Skills MCP server in PolicyLayer and add a rule for skills_run_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 Skills. Nothing to install.
skills_run_script 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 skills_run_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.
Set action: deny in the PolicyLayer policy for skills_run_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.
skills_run_script is provided by the Skills MCP server (jignesh-ponamwar/skills-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 →