Reset a configuration (parameter) to its default value. Use ros2_medkit_list_configurations first to see current parameter values.
AI agents call ros2_medkit_delete_configuration to permanently remove resources in Ros2 Medkit — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly overwrites configuration parameters by resetting them to defaults. While not data deletion in the traditional sense, resetting configurations destroys the current configuration state and cannot be undone without manual reconfiguration. This has high blast radius in a ROS 2 system where parameters control critical robot behavior, sensors, and safety settings.
From the tool's definition The tool description states 'Reset a configuration (parameter) to its default value,' which is an irreversible operation that overwrites existing configuration data and cannot be undone.
Documented attack patterns abuse exactly the kind of access ros2_medkit_delete_configuration gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ros2 Medkit, and nothing reaches the server without passing your rules. This is the rule we recommend for ros2_medkit_delete_configuration:
{
"version": "1",
"default": "deny",
"hide": [
"ros2_medkit_delete_configuration"
]
}ros2_medkit_delete_configuration disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Reset a configuration (parameter) to its default value. Use ros2_medkit_list_configurations first to see current parameter values. It is categorised as a Destructive tool in the Ros2 Medkit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ros2 Medkit MCP server in PolicyLayer and add a rule for ros2_medkit_delete_configuration: 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 Ros2 Medkit. Nothing to install.
ros2_medkit_delete_configuration 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 ros2_medkit_delete_configuration 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 ros2_medkit_delete_configuration. 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.
ros2_medkit_delete_configuration is provided by the Ros2 Medkit MCP server (selfpatch/ros2_medkit_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ros2 Medkit, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
84 Ros2 Medkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.