Ros2 Medkit

84 tools. 30 can modify or destroy data without limits.

9 destructive tools with no built-in limits. Policy required.

Last updated:

30 can modify or destroy data
54 read-only
84 tools total

Community server · catalogue entry verified 12/06/2026

How to control Ros2 Medkit ↓

What Ros2 Medkit exposes to your agents

Read (54) Write / Execute (21) Destructive / Financial (9)
Critical Risk

The most dangerous Ros2 Medkit tools

30 of Ros2 Medkit's 84 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Ros2 Medkit

PolicyLayer is an MCP gateway — it sits between your AI agents and Ros2 Medkit, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "ros2_medkit_bulkdata_delete": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "ros2_medkit_bulkdata_upload": {
    "limits": [
      {
        "counter": "ros2_medkit_bulkdata_upload_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "ros2_medkit_all_faults_list": {
    "limits": [
      {
        "counter": "ros2_medkit_all_faults_list_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Ros2 Medkit — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON ROS2 MEDKIT →

Free to start. No card required.

All 84 Ros2 Medkit tools

READ 54 tools
Read ros2_medkit_all_faults_list List all faults across the entire system. Returns faults from all components. Read ros2_medkit_apps_dependencies List dependencies for an app (other apps/components it depends on). Read ros2_medkit_apps_get Get detailed information about a specific app by its identifier. Read ros2_medkit_apps_list List all SOVD apps (ROS 2 nodes). Apps are individual ROS 2 nodes that can have operations, data, configuratio Read ros2_medkit_area_components List all components within a specific area. Use ros2_medkit_areas_list first to discover valid area IDs (e.g., Read ros2_medkit_area_contains List all entities contained in an area (components, apps, etc.). Read ros2_medkit_area_get Get detailed information about a specific area including its capabilities. Read ros2_medkit_area_subareas List sub-areas within an area. Use this to explore area hierarchy. Read ros2_medkit_areas_list List all SOVD areas (ROS 2 namespaces). Areas are top-level groupings like Read ros2_medkit_bulkdata_categories List available bulk-data categories for an entity. Bulk-data categories contain downloadable files like rosbag Read ros2_medkit_bulkdata_download Download a bulk-data file (e.g., rosbag recording) to the specified directory. Use the bulk_data_uri from faul Read ros2_medkit_bulkdata_download_for_fault Download all rosbag recordings associated with a specific fault. Retrieves the fault Read ros2_medkit_bulkdata_info Get information about a specific bulk-data item. Use the bulk_data_uri from fault environment_data snapshots. Read ros2_medkit_bulkdata_list List bulk-data items in a category. Use this to discover available rosbag recordings for download. Read ros2_medkit_component_dependencies List dependencies of a component. Read ros2_medkit_component_get Get detailed information about a specific component including its capabilities. Read ros2_medkit_component_hosts List apps hosted by a component. Read ros2_medkit_component_subcomponents List subcomponents of a component. Read ros2_medkit_components_list List all SOVD components (ROS 2 nodes) across all areas. Returns component IDs that can be used with other too Read ros2_medkit_data_categories List data categories for an entity (e.g., topics, parameters). Read ros2_medkit_data_groups List data groups for an entity. Read ros2_medkit_entities_get Get detailed information about a specific SOVD entity by its identifier, including live data if available. Use Read ros2_medkit_entities_list List all SOVD entities (areas and components combined) with optional substring filtering. This is the primary Read ros2_medkit_entity_data Read all topic data from an entity (returns all topics with their current values). Works with components, apps Read ros2_medkit_entity_topic_data Read data from a specific topic within an entity. Use ros2_medkit_entity_data first to discover available topi Read ros2_medkit_fault_snapshots Get diagnostic snapshots for a specific fault. Contains data captured at fault occurrence time. Read ros2_medkit_faults_get Get a specific fault by its code from an entity. First use ros2_medkit_faults_list to discover available fault Read ros2_medkit_faults_list List all faults for a specific entity. IMPORTANT: First use ros2_medkit_components_list or ros2_medkit_area_co Read ros2_medkit_functions_get Get detailed information about a specific function. Read ros2_medkit_functions_hosts List apps that host a specific function. Read ros2_medkit_functions_list List all SOVD functions. Functions are capability groupings that may be hosted by multiple apps. Read ros2_medkit_get_configuration Get a specific configuration (parameter) value. Use ros2_medkit_list_configurations first to discover availabl Read ros2_medkit_get_cyclic_sub Get details of a specific cyclic subscription. Read ros2_medkit_get_execution Get execution status and feedback for a specific execution. Use after ros2_medkit_create_execution to track ac Read ros2_medkit_get_lock Get details of a specific lock. Read ros2_medkit_get_log_configuration Get log configuration for an entity. Read ros2_medkit_get_operation Get details of a specific operation including its schema and capabilities. Read ros2_medkit_get_script Get details of a specific script. Read ros2_medkit_get_script_execution Get the status and result of a script execution. Read ros2_medkit_get_trigger Get details of a specific trigger by ID. Read ros2_medkit_get_update Get details of a registered update. Read ros2_medkit_get_update_status Get the current status of an update Read ros2_medkit_health Get health status of the SOVD gateway. Returns service status. Read ros2_medkit_list_configurations List all configurations (ROS 2 parameters) for an entity. Works with components, apps, areas, and functions. Read ros2_medkit_list_cyclic_subs List all cyclic subscriptions for an entity. Read ros2_medkit_list_executions List all executions for an operation. Use to see execution history and find execution IDs. Read ros2_medkit_list_locks List all active locks on an entity. Read ros2_medkit_list_logs List log entries for an entity. Returns recent log messages. Read ros2_medkit_list_operations List all operations (ROS 2 services and actions) available for an entity. Works with components, apps, areas, Read ros2_medkit_list_scripts List all scripts for an entity. Read ros2_medkit_list_triggers List all triggers for an entity. Triggers monitor resource changes and generate events. Read ros2_medkit_list_updates List all registered software updates. Read ros2_medkit_system_fault_snapshots Get system-wide diagnostic snapshots for a fault code. Read ros2_medkit_version Get the SOVD API version information from ros2_medkit gateway. Use this to verify the gateway is running.

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Ros2 Medkit

Can an AI agent delete data through the Ros2 Medkit MCP server? +

Yes. The Ros2 Medkit server exposes 9 destructive tools including ros2_medkit_bulkdata_delete, ros2_medkit_clear_all_faults, ros2_medkit_delete_all_configurations. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Ros2 Medkit? +

The Ros2 Medkit server has 11 write tools including ros2_medkit_bulkdata_upload, ros2_medkit_create_cyclic_sub, ros2_medkit_create_trigger. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Ros2 Medkit.

How many tools does the Ros2 Medkit MCP server expose? +

84 tools across 4 categories: Destructive, Execute, Read, Write. 54 are read-only. 30 can modify, create, or delete data.

How do I enforce a policy on Ros2 Medkit? +

Register the Ros2 Medkit MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Ros2 Medkit tool call.

Deterministic rules across all 84 Ros2 Medkit tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

84 Ros2 Medkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.