AI agents invoke send_program_script to trigger actions in Nonead Universal-Robots 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.
This tool sends arbitrary programs/scripts directly to a physical industrial robot (Universal Robots cobot). Executing arbitrary URScript on a robot arm can cause physical movement, collisions, equipment damage, or injury to nearby personnel. This is an Execute action with critical severity due to real-world physical consequences of misuse.
From the tool's definition 发送脚本到指定IP的机器人 (Send script to robot at specified IP)
Documented attack patterns abuse exactly the kind of access send_program_script gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nonead Universal-Robots MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for send_program_script:
{
"version": "1",
"default": "deny",
"tools": {
"send_program_script": {
"limits": [
{
"counter": "send_program_script_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} send_program_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.
Free to start. No card required.
发送脚本到指定IP的机器人。. It is categorised as a Execute tool in the Nonead Universal-Robots MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nonead Universal-Robots MCP Server MCP server in PolicyLayer and add a rule for send_program_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 Nonead Universal-Robots MCP Server. Nothing to install.
send_program_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 send_program_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 send_program_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.
send_program_script is provided by the Nonead Universal-Robots MCP Server MCP server (nonead/nonead-universal-robots-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nonead Universal-Robots MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 Nonead Universal-Robots MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.