Delete an access code from a lock
AI agents call delete_access_code to permanently remove resources in Seam MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes an access code from a smart lock, which cannot be undone. Deletion is irreversible and constitutes a destructive operation. While the impact is scoped to access credential management (not full system destruction), unauthorized deletion could lock out legitimate users or compromise security management.
From the tool's definition Tool name: 'delete_access_code'; description: 'Delete an access code from a lock'. The verb 'Delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete an access code from a lock. It is categorised as a Destructive tool in the Seam MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Seam MCP Server MCP server in PolicyLayer and add a rule for delete_access_code: 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.
delete_access_code is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_access_code 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 delete_access_code. 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.
delete_access_code 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 →