AI agents call ros2_medkit_delete_cyclic_sub 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.
The tool performs an irreversible deletion of a runtime subscription within a ROS 2 system. This fits the Destructive category definition—data/configuration that cannot be undone. While not directly hazardous like deleting safety-critical files, incorrect deletion of active subscriptions in a robotic system could disrupt monitoring, control loops, or fault detection, warranting high severity.
From the tool's definition Tool name contains 'delete' ("Delete a cyclic subscription"), which is an irreversible operation. Cyclic subscriptions are active ROS 2 system components; deletion cannot be undone without manual restoration.
Documented attack patterns abuse exactly the kind of access ros2_medkit_delete_cyclic_sub 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_cyclic_sub:
{
"version": "1",
"default": "deny",
"hide": [
"ros2_medkit_delete_cyclic_sub"
]
}ros2_medkit_delete_cyclic_sub 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.
Delete a cyclic subscription. 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_cyclic_sub: 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_cyclic_sub 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_cyclic_sub 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_cyclic_sub. 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_cyclic_sub 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.