lock_display

SERVERagentView SOURCEhttps://agentview.de/mcp

Medium RISK CLASS

Category Write

Parameters 21 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/de-agentview-agentview-mcp/lock-display.md

WHAT IT DOES

What lock_display does on agentView

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

Parameter	Type	Required	Description
`display_id`	string	Yes	The 8-character alphanumeric display profile ID to lock, e.g. 'ABCD1234'.
`access_token`	string	—	Optional bearer credential. Prefer passing session_request_id (from create_auth_session) instead; every tool accepts it and the server resolves it to your ident

Parameters from the server's own tool schema.

RISK

Why lock_display is rated Medium

The tool modifies the locked state of a display, which is a reversible write operation. It does not delete data (not Destructive), does not move money (not Financial), and does not execute arbitrary code (not Execute). While it affects access control, the core function is writing a lock state to the display configuration.

From the tool's definition lock_display modifies display state by setting a locked flag. The description states it 'Locks a display' and can be reversed with 'unlock_display', indicating a reversible state change rather than permanent deletion.

Risk signalsHandles credentials or secrets (access_token) · Admin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs lock_display safely

PolicyLayer is an MCP gateway: it sits between your AI agents and agentView, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lock_display, this is the rule to start with:

lock_display Rate-limited

lock_display 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": {
    "lock_display": {
      "limits": [
        {
          "counter": "lock_display_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect agentView, apply this rule, and every lock_display call is checked against it from then on.

FAQ

Questions about lock_display

What does the lock_display tool do? +

Locks a display so that content changes such as send_html, send_url and clear_display are rejected until unlock_display is called. Use this when the user wants to protect a display from accidental content changes. The display continues showing its current content. Requires admin scope. Returns id and locked (boolean true). To reverse this, use unlock_display. It is categorised as a Write tool in the agentView MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does lock_display accept? +

lock_display accepts 2 parameters: display_id, access_token. Required: display_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on lock_display? +

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

What risk level is lock_display? +

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

Can I rate-limit lock_display? +

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

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

lock_display is provided by the agentView MCP server (https://agentview.de/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on agentView, and thousands of servers like it.

This server

All 79 agentView tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →