Update an existing access code (change name, code, or time limits)
AI agents use update_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.
Updating access codes is a Write operation—it modifies configuration data without deletion. However, severity is high because misuse could grant unwanted access, disable legitimate codes, or create security gaps in physical access control systems. The blast radius extends to physical security and facility access for multiple lock brands.
From the tool's definition Tool explicitly updates/modifies an existing access code by changing 'name, code, or time limits'. This is a reversible modification that alters stored access control data.
Attacks that exploit this kind of access
Update an existing access code (change name, code, or 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 update_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.
update_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 update_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 update_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.
update_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 →