AI agents call dji_disconnect to permanently remove resources in Robot — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Disconnecting from an active drone mid-operation could cause loss of control, leading to a crash or fly-away — an irreversible physical outcome. The sibling tools include takeoff/land/emergency_stop, confirming this is a live hardware control context. While 'disconnect' could be a soft session teardown, in an aerial robotics context it carries high blast radius. Confidence is moderate due to the empty description.
From the tool's definition Tool name 'dji_disconnect' on a drone-control server; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access dji_disconnect 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_disconnect:
{
"version": "1",
"default": "deny",
"hide": [
"dji_disconnect"
]
}dji_disconnect disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
dji_disconnect. It is categorised as a Destructive tool in the Robot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Robot MCP server in PolicyLayer and add a rule for dji_disconnect: 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_disconnect is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the dji_disconnect 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_disconnect. 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_disconnect 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.