Show definition of a ROS interface
AI agents call show_interface to retrieve information from ROS 2 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays metadata about ROS interface definitions. It performs a read-only query operation with no side effects, no code execution, no data modification, and no destructive actions. The low severity reflects minimal blast radius even if misused by an AI agent—displaying interface definitions cannot cause harm to the ROS 2 system.
From the tool's definition Tool name 'show_interface' with description 'Show definition of a ROS interface' indicates a retrieval operation that displays interface definitions without modification or execution.
Attacks that exploit this kind of access
Show definition of a ROS interface. It is categorised as a Read tool in the ROS 2 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ROS 2 MCP Server MCP server in PolicyLayer and add a rule for show_interface: 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 2 MCP Server. Nothing to install.
show_interface 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 show_interface 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 show_interface. 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.
show_interface is provided by the ROS 2 MCP Server MCP server (ranch-hand-robotics/rde-mcp-ros-2). 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 →