List iOS devices and simulators visible to Xcode. Use this first when you do not know the exact deviceId. Pass the returned device id or name to runcue_run/runcue_check; do not use the ambiguous value \
AI agents call runcue_devices to retrieve information from RunCue without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves a list of iOS devices and simulators without modifying any state, executing code, or performing destructive operations. It is purely informational and read-only in nature, making it a Read category tool with low severity risk.
From the tool's definition List iOS devices and simulators visible to Xcode. Use this first when you do not know the exact deviceId.
Attacks that exploit this kind of access
List iOS devices and simulators visible to Xcode. Use this first when you do not know the exact deviceId. Pass the returned device id or name to runcue_run/runcue_check; do not use the ambiguous value \. It is categorised as a Read tool in the RunCue MCP Server, which means it retrieves data without modifying state.
Register the RunCue MCP server in PolicyLayer and add a rule for runcue_devices: 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 RunCue. Nothing to install.
runcue_devices 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 runcue_devices 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 runcue_devices. 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.
runcue_devices is provided by the RunCue MCP server (lihei12345/runcue). 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 →