AI agents invoke dji_takeoff 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.
Initiating drone takeoff is a physical world action with real-world consequences — the drone becomes airborne. While not irreversibly destructive in the data sense, it triggers an external physical operation whose effects depend on the environment and could cause harm. The empty description lowers confidence slightly, but the name and server context make the classification clear.
From the tool's definition Tool name 'dji_takeoff' on a server that 'enabling LLMs to control Unitree robots and DJI Tello drones'; description is empty but context from sibling tools (dji_takeoff_hover_land, dji_land, dji_emergency_stop) strongly implies this initiates drone…
Documented attack patterns abuse exactly the kind of access dji_takeoff 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 dji_takeoff:
{
"version": "1",
"default": "deny",
"tools": {
"dji_takeoff": {
"limits": [
{
"counter": "dji_takeoff_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}dji_takeoff 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.
dji_takeoff. 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 dji_takeoff: 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.
dji_takeoff 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 dji_takeoff 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 dji_takeoff. 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.
dji_takeoff 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.