AI agents invoke run to trigger actions in Mycobot. 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.
This tool executes external operations (physical robot movements) whose effects depend on arguments and cannot be easily predicted without seeing the actual parameters. A misused 'run' command could cause the robot arm to move unexpectedly, knock over objects, damage equipment, or injure nearby persons. While not permanently destructive in data terms, the physical consequences are severe.
From the tool's definition Tool name 'run' on a myCobot robot control server with sibling tools for capture, detection, and robot settings. The server's stated purpose is 'sending pick-and-place instructions' to a physical robotic arm.
Documented attack patterns abuse exactly the kind of access run gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mycobot, and nothing reaches the server without passing your rules. This is the rule we recommend for run:
{
"version": "1",
"default": "deny",
"tools": {
"run": {
"limits": [
{
"counter": "run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run 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.
run. It is categorised as a Execute tool in the Mycobot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mycobot MCP server in PolicyLayer and add a rule for run: 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 Mycobot. Nothing to install.
run 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 run 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 run. 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.
run is provided by the Mycobot MCP server (neka-nat/mycobot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mycobot, 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 Mycobot tools catalogued and risk-classified — across an index of 43,000+ MCP servers.