list_robot_capabilities
AI agents call list_robot_capabilities to retrieve information from Robot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and context (sibling tools are control operations like dji_takeoff, dji_land) suggest this is an informational read operation that lists available capabilities or status. Despite the empty description lowering confidence slightly, the name strongly indicates a non-destructive information retrieval function. No severity concern since listing capabilities has no side effects on the robots or environment.
From the tool's definition Tool name 'list_robot_capabilities' indicates a query/enumeration operation that retrieves capability information without modifying state or triggering actions.
Documented attack patterns abuse exactly the kind of access list_robot_capabilities 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 list_robot_capabilities:
{
"version": "1",
"default": "deny",
"tools": {
"list_robot_capabilities": {}
}
}list_robot_capabilities is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
list_robot_capabilities. It is categorised as a Read tool in the Robot MCP Server, which means it retrieves data without modifying state.
Register the Robot MCP server in PolicyLayer and add a rule for list_robot_capabilities: 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.
list_robot_capabilities is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_robot_capabilities 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 list_robot_capabilities. 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.
list_robot_capabilities 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.