Get the current lock status (locked/unlocked) of a specific lock
AI agents call get_lock_status to retrieve information from Seam MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the current status of a smart lock (locked/unlocked state) with no side effects. It is a pure read operation that queries data. Even though the broader Seam MCP server controls physical security devices, this specific tool only observes state and poses minimal risk if misused by an AI agent—the worst outcome would be unnecessary status checks consuming API quota or providing incorrect information…
From the tool's definition Tool name 'get_lock_status' and description 'Get the current lock status (locked/unlocked) of a specific lock' indicate a query operation that retrieves state information without modifying or triggering any actions.
Attacks that exploit this kind of access
Get the current lock status (locked/unlocked) of a specific lock. It is categorised as a Read tool in the Seam MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Seam MCP Server MCP server in PolicyLayer and add a rule for get_lock_status: 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 Seam MCP Server. Nothing to install.
get_lock_status 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_lock_status 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_lock_status. 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_lock_status is provided by the Seam MCP Server MCP server (keithah/seam-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 →