Lists available ROS services
AI agents call list_services 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 queries and enumerates ROS 2 services without modifying, executing, or deleting any system state. It is a pure introspection/discovery operation analogous to 'list' or 'get' operations. The blast radius of misuse is minimal — an AI agent cannot cause harm by listing available services. This is characteristic of Read category tools.
From the tool's definition Tool name is 'list_services' and description states it 'Lists available ROS services' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
Lists available ROS services. 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 list_services: 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.
list_services 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_services 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_services. 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_services 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 →