List available launch files in a ROS package
AI agents call list_launch_files 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 enumerates launch file metadata from a ROS package without modifying, executing, or deleting any resources. It is purely informational and has no downstream effects on the ROS system state.
From the tool's definition Tool name 'list_launch_files' and description 'List available launch files in a ROS package' indicate a query/retrieval operation with no side effects. The verb 'list' is a read-only introspection action.
Attacks that exploit this kind of access
List available launch files in a ROS package. 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_launch_files: 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_launch_files 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_launch_files 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_launch_files. 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_launch_files 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 →