List UiPath machines registered in the Orchestrator tenant.
AI agents call list_machines to retrieve information from UiPath MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about machines without side effects. It falls squarely into the Read category as it queries existing data. The severity is low because exposure of machine inventory in an orchestration platform, while potentially informative to an attacker, does not directly enable destructive or financial harm without further action through other tools.
From the tool's definition Tool name 'list_machines' and description 'List UiPath machines registered in the Orchestrator tenant' indicate a query/retrieval operation with no modification or execution.
Attacks that exploit this kind of access
List UiPath machines registered in the Orchestrator tenant. It is categorised as a Read tool in the UiPath MCP Server MCP Server, which means it retrieves data without modifying state.
Register the UiPath MCP Server MCP server in PolicyLayer and add a rule for list_machines: 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 UiPath MCP Server. Nothing to install.
list_machines is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_machines 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 list_machines. 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.
list_machines is provided by the UiPath MCP Server MCP server (lokimcpuniverse/uipath-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 →