Shows detailed information about a specific ROS 2 node.
AI agents call get_ros2_node_info to retrieve information from ROS MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs information retrieval about ROS 2 nodes with no side effects. It matches the Read category pattern of querying/fetching data. The severity is low because even if an AI agent misuses this to inspect nodes, it cannot modify, delete, or execute arbitrary operations—it only exposes visibility into the system topology and node status.
From the tool's definition Tool name 'get_ros2_node_info' and description 'Shows detailed information about a specific ROS 2 node' indicate a read-only query operation that retrieves and displays node metadata without modifying any state.
Documented attack patterns abuse exactly the kind of access get_ros2_node_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ROS MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_ros2_node_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_ros2_node_info": {}
}
}get_ros2_node_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Shows detailed information about a specific ROS 2 node. It is categorised as a Read tool in the ROS MCP MCP Server, which means it retrieves data without modifying state.
Register the ROS MCP server in PolicyLayer and add a rule for get_ros2_node_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 ROS MCP. Nothing to install.
get_ros2_node_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 get_ros2_node_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 get_ros2_node_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.
get_ros2_node_info is provided by the ROS MCP server (yutarop/ros-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 ROS MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
24 ROS MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.