AI agents invoke learn_run_script to trigger actions in SkillMCP. 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.
The tool name explicitly contains 'run_script', which maps to the Execute category (runs code or triggers external operations whose effects depend on arguments). Though the description is empty, the naming convention and server purpose (serving skills and behavioral rules to coding assistants) strongly indicate this tool executes arbitrary scripts.
From the tool's definition Tool name 'learn_run_script' indicates script execution capability. The server context confirms it injects behavioral rules and knowledge into AI agents for coding assistance, and sibling tools (read_skill, read_skill_file, list_skills) suggest this tool…
Attacks that exploit this kind of access
learn_run_script. It is categorised as a Execute tool in the SkillMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Skill MCP server in PolicyLayer and add a rule for learn_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 SkillMCP. Nothing to install.
learn_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 learn_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 learn_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.
learn_run_script is provided by the Skill MCP server (nventimiglia/skillsmcp). 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 →