Set alarm mode
AI agents invoke abode_set_mode to trigger actions in Garza Home MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Setting an alarm mode on a home security system (e.g., arming/disarming, home/away/night modes) triggers an external physical security operation. This is not a simple data write — it directly affects the armed state of the security system, with significant real-world consequences if misused (e.g., disarming a security system leaves the home unprotected).
From the tool's definition "Set alarm mode" — actively changes the operational state of a home security/alarm system
Attacks that exploit this kind of access
Set alarm mode. It is categorised as a Execute tool in the Garza Home MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Garza Home MCP server in PolicyLayer and add a rule for abode_set_mode: 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_set_mode is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the abode_set_mode 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_set_mode. 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_set_mode 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 →