abode_lock_device · Garza Home MCP: Risk & Policy

WHAT IT DOES

What abode_lock_device does on Garza Home MCP

AI agents invoke abode_lock_device 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.

WHY IT NEEDS A POLICY

Why abode_lock_device needs a policy

This tool actuates a physical lock or unlock action on a home security device. It causes a real-world side effect (changing the physical lock state of a door or similar device) that goes beyond a simple data write. Misuse could result in unauthorized physical access to the home (unlocking) or lockouts (locking), making it high severity.

From the tool's definition Lock/unlock device — triggers a physical state change on a home security device

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

abode_lock_device Rate-limited

abode_lock_device stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "abode_lock_device": {
      "limits": [
        {
          "counter": "abode_lock_device_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Garza Home MCP, so you can run agents against it safely.

FAQ

Questions about abode_lock_device

What does the abode_lock_device tool do? +

Lock/unlock device. 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.

How do I enforce a policy on abode_lock_device? +

Register the Garza Home MCP server in PolicyLayer and add a rule for abode_lock_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.

What risk level is abode_lock_device? +

abode_lock_device is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit abode_lock_device? +

Yes. Add a rate_limit block to the abode_lock_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.

How do I block abode_lock_device completely? +

Set action: deny in the PolicyLayer policy for abode_lock_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.

What MCP server provides abode_lock_device? +

abode_lock_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.