Call a ROS service
AI agents invoke publish_service to trigger actions in Rosbridge 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.
Calling a ROS service is an active operation that executes commands on a ROS-based robotics system. The effects are highly variable and argument-dependent — services can trigger robot motion, sensor configuration, state changes, or other physical/system-level actions. This is an Execute-category action with high severity because misuse could cause physical harm, equipment damage, or unintended robot behavior.
From the tool's definition 'Call a ROS service' - invoking a ROS service triggers external operations on a robotics system whose effects depend entirely on which service is called and its arguments
Attacks that exploit this kind of access
Call a ROS service. It is categorised as a Execute tool in the Rosbridge MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Rosbridge MCP Server MCP server in PolicyLayer and add a rule for publish_service: 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 Rosbridge MCP Server. Nothing to install.
publish_service 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 publish_service 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 publish_service. 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.
publish_service is provided by the Rosbridge MCP Server MCP server (takanarishimbo/rosbridge-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →