AI agents use create_collaborative_task to create or update resources in Nonead Universal-Robots MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nonead Universal-Robots MCP Server environment.
The tool 'creates' a collaborative task for multiple robots, which is a Write operation (creating a new task/configuration). However, given the context of physical robot control, the severity is high because incorrectly created collaborative tasks could lead to unsafe robot movements or collisions. The tool appears to define/schedule tasks rather than immediately execute them, placing it in Write rather than Execute.
From the tool's definition 创建多机器人协同任务 (Create multi-robot collaborative task)
Documented attack patterns abuse exactly the kind of access create_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 create_collaborative_task:
{
"version": "1",
"default": "deny",
"tools": {
"create_collaborative_task": {
"limits": [
{
"counter": "create_collaborative_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_collaborative_task stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
创建多机器人协同任务. It is categorised as a Write tool in the Nonead Universal-Robots MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nonead Universal-Robots MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_collaborative_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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.