Get device details
AI agents call abode_get_device to retrieve information from Garza Home MCP 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 a device from the Abode home security system. It performs a query operation with no side effects—it does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal; an attacker would only gain visibility into device configuration or status, not the ability to control devices or affect system state. Read classification is appropriate.
From the tool's definition Tool name 'abode_get_device' with description 'Get device details' indicates retrieval of existing data without modification. The verb 'get' and context of querying device information from a home security system (Abode) confirm this is a read-only operation.
Attacks that exploit this kind of access
Get device details. It is categorised as a Read tool in the Garza Home MCP MCP Server, which means it retrieves data without modifying state.
Register the Garza Home MCP server in PolicyLayer and add a rule for abode_get_device: 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 Garza Home MCP. Nothing to install.
abode_get_device 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 abode_get_device 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 abode_get_device. 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.
abode_get_device is provided by the Garza Home MCP server (itsablabla/garza-home-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 →