Trigger emergency stop on robot. Immediate halt with guaranteed <10ms response.
AI agents invoke nwo_emergency_stop to trigger actions in NWO Robotics. 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 executes an external operation (emergency halt) on physical robots whose effects depend on robot state and environment. While the action itself is defensive (stopping motion), it qualifies as Execute rather than Read/Write because it triggers real-time hardware control with immediate irreversible mechanical effects. It is not Destructive because emergency stop is reversible via subsequent commands.
From the tool's definition Tool name 'nwo_emergency_stop' and description 'Trigger emergency stop on robot. Immediate halt with guaranteed <10ms response' indicate execution of a real-world control command on physical hardware with immediate effects.
Attacks that exploit this kind of access
Trigger emergency stop on robot. Immediate halt with guaranteed <10ms response. It is categorised as a Execute tool in the NWO Robotics MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the NWO Robotics MCP server in PolicyLayer and add a rule for nwo_emergency_stop: 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 NWO Robotics. Nothing to install.
nwo_emergency_stop 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 nwo_emergency_stop 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 nwo_emergency_stop. 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.
nwo_emergency_stop is provided by the NWO Robotics MCP server (redciprianpater/mcp-server-robotics). 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 →