机器人右转
AI agents invoke joy_turn_right to trigger actions in ROS 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 executes a real-world physical action (rotating a robot) whose effects depend on the robot's physical environment and cannot be trivially undone. While not irreversible in the destructive sense, it triggers external robot operations with tangible physical consequences.
From the tool's definition Tool name 'joy_turn_right' combined with description '机器人右转' (robot turn right) indicates a command that executes a physical robot action.
Attacks that exploit this kind of access
机器人右转. It is categorised as a Execute tool in the ROS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ROS MCP Server MCP server in PolicyLayer and add a rule for joy_turn_right: 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 ROS MCP Server. Nothing to install.
joy_turn_right 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 joy_turn_right 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 joy_turn_right. 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.
joy_turn_right is provided by the ROS MCP Server MCP server (moneypiaorui/ros-mcp-server-minipi). 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 →