AI agents call ros2_medkit_list_locks to retrieve information from Ros2 Medkit 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 operation that retrieves the status of existing locks. It has no side effects, does not execute code or commands, does not modify data, and does not delete or commit financial obligations. The blast radius of misuse is minimal—an agent could only gain information about lock status on ROS 2 system entities.
From the tool's definition Tool name contains 'list' and description states 'List all active locks on an entity' - this is a query operation that retrieves information without modifying any state or triggering operations.
Documented attack patterns abuse exactly the kind of access ros2_medkit_list_locks 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_list_locks:
{
"version": "1",
"default": "deny",
"tools": {
"ros2_medkit_list_locks": {}
}
}ros2_medkit_list_locks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all active locks on an entity. It is categorised as a Read tool in the Ros2 Medkit MCP Server, which means it retrieves data without modifying state.
Register the Ros2 Medkit MCP server in PolicyLayer and add a rule for ros2_medkit_list_locks: 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_list_locks 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 ros2_medkit_list_locks 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_list_locks. 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_list_locks 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.