Medium Risk

lock_elements

Lock elements to prevent modification

How to control lock_elements ↓

AI agents use lock_elements to create or update resources in Excalidraw MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Excalidraw MCP Server environment.

Medium Risk

Locking elements is a reversible modification operation that changes the metadata/state of existing diagram components. It does not delete data (ruling out Destructive), execute external code (ruling out Execute), or involve financial transactions (ruling out Financial). While it prevents further modification of those elements, the lock itself is a Write operation that can be undone by unlocking.

From the tool's definition Tool name 'lock_elements' and description 'Lock elements to prevent modification' indicate a state-change operation on diagram elements that modifies their properties (locking status) without creating or deleting content.

Documented attack patterns abuse exactly the kind of access lock_elements gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Excalidraw MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for lock_elements:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "lock_elements": {
      "limits": [
        {
          "counter": "lock_elements_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Excalidraw MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the lock_elements tool do? +

Lock elements to prevent modification. It is categorised as a Write tool in the Excalidraw 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 lock_elements? +

Register the Excalidraw MCP Server MCP server in PolicyLayer and add a rule for lock_elements: 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 Excalidraw MCP Server. Nothing to install.

What risk level is lock_elements? +

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

Can I rate-limit lock_elements? +

Yes. Add a rate_limit block to the lock_elements 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 lock_elements completely? +

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

lock_elements is provided by the Excalidraw MCP Server MCP server (yctimlin/mcp_excalidraw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Excalidraw MCP Server tool call.

Deterministic rules across all 26 Excalidraw MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

26 Excalidraw MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.