Get the device ID
AI agents call get_device_id to retrieve information from AutoBot MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static device identification information with no side effects, no code execution, and no data modification. It is a simple informational query that fits the 'Read' category. The severity is low because device IDs are typically non-sensitive identifiers and their disclosure carries minimal risk. The confidence is high because the intent and behavior are unambiguous.
From the tool's definition Tool name 'get_device_id' and description 'Get the device ID' indicate a retrieval operation that queries device information without modifying or executing operations on the device.
Attacks that exploit this kind of access
Get the device ID. It is categorised as a Read tool in the AutoBot MCP MCP Server, which means it retrieves data without modifying state.
Register the AutoBot MCP server in PolicyLayer and add a rule for get_device_id: 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 AutoBot MCP. Nothing to install.
get_device_id 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 get_device_id 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 get_device_id. 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.
get_device_id is provided by the AutoBot MCP server (yz0903/autobot-mcp). 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 →