Check if a ROS parameter exists.
AI agents call ros_has_param 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 performs a read-only existence check on ROS parameters. It retrieves information without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent cannot cause harm by checking parameter existence. This aligns with the Read category for data retrieval with no side effects.
From the tool's definition Tool name 'ros_has_param' and description 'Check if a ROS parameter exists' indicate a query operation that only checks for parameter existence without modification or side effects.
Attacks that exploit this kind of access
Check if a ROS parameter exists. 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_has_param: 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_has_param 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_has_param 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_has_param. 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_has_param 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 →