List all smart locks connected to your Seam account
AI agents call list_locks 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 information about existing smart locks without modifying, deleting, or executing any actions. It is a read-only operation that simply enumerates devices, making it the least risky category. Severity is low because access to a list of locks does not directly enable unauthorized physical access or other high-impact misuse without additional tools like unlock_door.
From the tool's definition Tool name 'list_locks' and description 'List all smart locks connected to your Seam account' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List all smart locks connected to your Seam account. 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 list_locks: 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.
list_locks 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 list_locks 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 list_locks. 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.
list_locks 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 →