Delete a ROS parameter.
AI agents call ros_delete_param to permanently remove resources in ROS1 Noetic MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting ROS parameters is an irreversible action that destroys configuration state. A robotic system relying on specific parameters for operation (e.g., safety limits, sensor calibration, network endpoints) could become inoperable or unsafe if critical parameters are deleted by a misdirected agent.
From the tool's definition Tool name 'ros_delete_param' combined with description 'Delete a ROS parameter' indicates irreversible removal of configuration data.
Attacks that exploit this kind of access
Delete a ROS parameter. It is categorised as a Destructive tool in the ROS1 Noetic MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ROS1 Noetic MCP Server MCP server in PolicyLayer and add a rule for ros_delete_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_delete_param is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the ros_delete_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_delete_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_delete_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 →