Get information about a ROS action
AI agents call get_action_info 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 metadata about ROS actions without triggering them, modifying system state, or executing arbitrary code. It is purely informational, similar to sibling tools like 'get_node_info', 'get_nodes', and 'get_package_manifest' which are all Read operations. The blast radius of misuse is minimal—an AI could only gather information about available actions.
From the tool's definition Tool name 'get_action_info' and description 'Get information about a ROS action' indicate a read-only retrieval operation. The verb 'Get' paired with 'information' shows data querying without modification or execution.
Attacks that exploit this kind of access
Get information about a ROS action. 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 get_action_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 2 MCP Server. Nothing to install.
get_action_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_action_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_action_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_action_info 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 →