Show the definition of a ROS service type.
AI agents call ros_show_srv 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 and displays the definition/schema of a ROS service type. It is a read-only inspection operation that retrieves metadata about available services. No side effects, no data modification, no code execution, and no irreversible changes. It is analogous to 'get' or 'describe' operations. The low severity reflects minimal risk even if an LLM agent calls it repeatedly or on arbitrary service types.
From the tool's definition Tool name 'ros_show_srv' and description 'Show the definition of a ROS service type' indicate inspection/retrieval of service metadata without modification or execution.
Attacks that exploit this kind of access
Show the definition of a ROS service type. 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_show_srv: 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_show_srv 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_show_srv 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_show_srv. 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_show_srv 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 →