run_package_executable · ROS 2 MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_package_executable does on ROS 2 MCP Server

AI agents invoke run_package_executable to trigger actions in ROS 2 MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_package_executable needs a policy

This tool triggers execution of ROS package executables, which can run arbitrary code with the permissions of the ROS process. The impact depends entirely on what executable is chosen and its arguments.

From the tool's definition Tool name 'run_package_executable' and description 'Run a ROS package executable' directly indicates execution of arbitrary external code/processes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_package_executable Rate-limited

run_package_executable stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_package_executable": {
      "limits": [
        {
          "counter": "run_package_executable_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ROS 2 MCP Server, so you can run agents against it safely.

FAQ

Questions about run_package_executable

What does the run_package_executable tool do? +

Run a ROS package executable. It is categorised as a Execute tool in the ROS 2 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_package_executable? +

Register the ROS 2 MCP Server MCP server in PolicyLayer and add a rule for run_package_executable: 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 ROS 2 MCP Server. Nothing to install.

What risk level is run_package_executable? +

run_package_executable is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_package_executable? +

Yes. Add a rate_limit block to the run_package_executable 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.

How do I block run_package_executable completely? +

Set action: deny in the PolicyLayer policy for run_package_executable. 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.

What MCP server provides run_package_executable? +

run_package_executable is provided by the ROS 2 MCP Server MCP server (ranch-hand-robotics/rde-mcp-ros-2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.