Create an access code on a specific lock with optional time limits
AI agents use create_access_code to create or update resources in Seam MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Seam MCP Server environment.
This tool creates new access codes, which is a write operation as it creates new data/credentials on smart locks. It is reversible (codes can be deleted via delete_access_code) so it does not qualify as Destructive. However, it is high severity because unauthorized creation of access codes could grant unintended access to physical locks, creating a significant security and safety risk if misused by an AI agent.
From the tool's definition Tool creates access codes on locks with optional time limits. The description states 'Create an access code' which is a reversible write operation that generates new authentication credentials.
Attacks that exploit this kind of access
Create an access code on a specific lock with optional time limits. It is categorised as a Write tool in the Seam MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Seam MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_access_code is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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 →