AI agents invoke stop_data_recording 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.
Stopping a data recording process is an Execute action because it triggers an external operation that changes the state of the robot system (halts recording). While not destructive (the data already collected remains), it represents active control over robot behavior.
From the tool's definition Tool name 'stop_data_recording' indicates control over an active recording process on a Universal Robots cobot system. The description '停止数据记录' (Chinese: 'stop data recording') confirms it halts an ongoing operation.
Documented attack patterns abuse exactly the kind of access stop_data_recording 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 stop_data_recording:
{
"version": "1",
"default": "deny",
"tools": {
"stop_data_recording": {
"limits": [
{
"counter": "stop_data_recording_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_data_recording 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 stop_data_recording: 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.
stop_data_recording 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 stop_data_recording 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 stop_data_recording. 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.
stop_data_recording 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.