run_routine_sequence
AI agents invoke run_routine_sequence to trigger actions in Robot. 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 sequences of commands on physical robotic systems. While 'routine' suggests predefined behavior, executing sequences on hardware has consequences dependent on what those sequences contain—they can move robots, consume energy, and interact with the physical environment.
From the tool's definition Tool name 'run_routine_sequence' combined with server purpose of controlling physical robots (Unitree robots, DJI Tello drones) and sibling tools that execute drone actions (dji_takeoff, dji_land, dji_perimeter_scan).
Documented attack patterns abuse exactly the kind of access run_routine_sequence gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Robot, and nothing reaches the server without passing your rules. This is the rule we recommend for run_routine_sequence:
{
"version": "1",
"default": "deny",
"tools": {
"run_routine_sequence": {
"limits": [
{
"counter": "run_routine_sequence_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_routine_sequence 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.
run_routine_sequence. It is categorised as a Execute tool in the Robot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Robot MCP server in PolicyLayer and add a rule for run_routine_sequence: 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 Robot. Nothing to install.
run_routine_sequence 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 run_routine_sequence 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 run_routine_sequence. 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.
run_routine_sequence is provided by the Robot MCP server (showkeyjar/robot-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Robot, 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.
24 Robot tools catalogued and risk-classified — across an index of 43,000+ MCP servers.