List available ROS service types.
AI agents call ros_list_srv_types to retrieve information from ROS1 Noetic 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 lists available ROS service types—a query operation that discovers system metadata without side effects. It does not execute services, modify parameters, delete resources, or trigger external operations. The action is purely informational, analogous to a directory listing or schema introspection. No data is created, modified, deleted, or financial value is affected.
From the tool's definition Tool name 'ros_list_srv_types' and description 'List available ROS service types' indicate read-only enumeration of service metadata with no state modification or execution.
Attacks that exploit this kind of access
List available ROS service types. It is categorised as a Read tool in the ROS1 Noetic MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ROS1 Noetic MCP Server MCP server in PolicyLayer and add a rule for ros_list_srv_types: 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 ROS1 Noetic MCP Server. Nothing to install.
ros_list_srv_types 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 ros_list_srv_types 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 ros_list_srv_types. 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.
ros_list_srv_types is provided by the ROS1 Noetic MCP Server MCP server (lopisan/ros-mcp). 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 →