create_access_code_on_multiple_locks

WHAT IT DOES

What create_access_code_on_multiple_locks does on Seam MCP Server

AI agents use create_access_code_on_multiple_locks 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.

WHY IT NEEDS A POLICY

Why create_access_code_on_multiple_locks needs a policy

This tool creates new access codes across multiple physical locks, which is a reversible modification operation (codes can be deleted via delete_access_code). While it modifies security-sensitive systems, the action itself is not destructive or financial—it's a write operation that changes lock access configurations.

From the tool's definition The tool creates access codes on multiple locks, as stated in the description: 'Create the same access code on multiple locks.' This is explicitly a creation operation that modifies lock systems.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_access_code_on_multiple_locks Rate-limited

create_access_code_on_multiple_locks stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_access_code_on_multiple_locks": {
      "limits": [
        {
          "counter": "create_access_code_on_multiple_locks_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Seam MCP Server, so you can run agents against it safely.

FAQ

Questions about create_access_code_on_multiple_locks

What does the create_access_code_on_multiple_locks tool do? +

Create the same access code on multiple locks (useful for creating one code for all locks in a location). 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.

How do I enforce a policy on create_access_code_on_multiple_locks? +

Register the Seam MCP Server MCP server in PolicyLayer and add a rule for create_access_code_on_multiple_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.

What risk level is create_access_code_on_multiple_locks? +

create_access_code_on_multiple_locks is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_access_code_on_multiple_locks? +

Yes. Add a rate_limit block to the create_access_code_on_multiple_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.

How do I block create_access_code_on_multiple_locks completely? +

Set action: deny in the PolicyLayer policy for create_access_code_on_multiple_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.

What MCP server provides create_access_code_on_multiple_locks? +

create_access_code_on_multiple_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.