Get the display name of the device
AI agents call get_device_name 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 device information (the display name) without modifying, executing operations, deleting data, or affecting financial systems. It is a straightforward query operation with minimal blast radius if misused—an agent could only learn the device's name, which is non-sensitive metadata. Low severity is appropriate for passive information retrieval.
From the tool's definition Tool name 'get_device_name' and description 'Get the display name of the device' indicate a retrieval operation with no side effects. The verb 'Get' and the read-only nature of querying device metadata confirm this is a data retrieval action.
Attacks that exploit this kind of access
Get the display name of the device. 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_name: 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_name 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_name 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_name. 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_name 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 →