Get detailed information about a ROS service.
AI agents call ros_get_service_info 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 queries metadata about ROS services without modifying state, executing code, or triggering service operations. It is purely informational, analogous to inspection or metadata retrieval. The low severity reflects minimal blast radius—incorrect usage returns incomplete or erroneous service metadata rather than operational harm to the robotic system.
From the tool's definition Tool is named 'ros_get_service_info' and described as retrieving 'detailed information about a ROS service'. The verb 'get' and action of retrieving information with no mention of modification, deletion, or execution indicates a read operation.
Attacks that exploit this kind of access
Get detailed information about a ROS service. 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_get_service_info: 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_get_service_info 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_get_service_info 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_get_service_info. 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_get_service_info 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 →