AI agents invoke sim_fleet_route to trigger actions in Robotics 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.
The tool name suggests routing commands to a fleet of simulated or physical robots. Given the server context — unified control of physical and virtual robots, multi-robot coordination — this tool likely sends movement/routing commands to robot fleets, which constitutes executing external operations. However, the empty description significantly lowers confidence.
From the tool's definition Tool name 'sim_fleet_route' on a robotics MCP server that controls both physical robots (ROS-based) and virtual robots. No description provided.
Documented attack patterns abuse exactly the kind of access sim_fleet_route gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Robotics MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for sim_fleet_route:
{
"version": "1",
"default": "deny",
"tools": {
"sim_fleet_route": {
"limits": [
{
"counter": "sim_fleet_route_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}sim_fleet_route 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.
Free to start. No card required.
sim_fleet_route. It is categorised as a Execute tool in the Robotics MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Robotics MCP Server MCP server in PolicyLayer and add a rule for sim_fleet_route: 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 Robotics MCP Server. Nothing to install.
sim_fleet_route is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sim_fleet_route 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 sim_fleet_route. 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.
sim_fleet_route is provided by the Robotics MCP Server MCP server (sandraschi/robotics-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Robotics MCP Server, 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.
5 Robotics MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.