AI agents invoke execute_collaborative_task 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 triggers real-time control of physical cobots (collaborative robots) to perform coordinated tasks. The effects are dependent on task parameters and cannot be fully predicted without knowing the specific task instructions. Physical robot execution represents a significant blast radius: misconfigured or adversarial task definitions could cause equipment damage, unsafe movements, or workplace hazards.
From the tool's definition Tool name 'execute_collaborative_task' combined with server description stating it 'Enables natural language control of Universal Robots cobots' and 'supporting real-time motion commands' indicates the tool executes external operations on physical robotic…
Documented attack patterns abuse exactly the kind of access execute_collaborative_task 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 execute_collaborative_task:
{
"version": "1",
"default": "deny",
"tools": {
"execute_collaborative_task": {
"limits": [
{
"counter": "execute_collaborative_task_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_collaborative_task 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.
执行多机器人协同任务. 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 execute_collaborative_task: 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.
execute_collaborative_task 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 execute_collaborative_task 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 execute_collaborative_task. 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.
execute_collaborative_task 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.