navigate_to_poses · Ros MCP: Risk & Policy

WHAT IT DOES

What navigate_to_poses does on Ros

AI agents invoke navigate_to_poses to trigger actions in Ros. 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 navigate_to_poses needs a policy

This tool executes external operations (robot navigation) with side effects that depend on supplied arguments (target poses). While not destructive or financial, it meets the Execute category definition: 'runs code, shell commands, browser actions, or triggers external operations whose effects depend on arguments.' The severity is high because misuse could cause physical robots to navigate to unsafe locations,…

From the tool's definition Sends a Nav2 NavigateToPoses command over MQTT to control autonomous mobile robots (AMRs). This triggers real-world motion and navigation actions in physical robots whose effects depend entirely on the pose arguments provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

navigate_to_poses Rate-limited

navigate_to_poses 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": {
    "navigate_to_poses": {
      "limits": [
        {
          "counter": "navigate_to_poses_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, so you can run agents against it safely.

FAQ

Questions about navigate_to_poses

What does the navigate_to_poses tool do? +

Send a Nav2 NavigateToPoses-style command over MQTT. It is categorised as a Execute tool in the Ros MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on navigate_to_poses? +

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

What risk level is navigate_to_poses? +

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

Can I rate-limit navigate_to_poses? +

Yes. Add a rate_limit block to the navigate_to_poses 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 navigate_to_poses completely? +

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

navigate_to_poses is provided by the Ros MCP server (reidlo5135/ros-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.