create_display
Pre-provisions a display without hardware, personal or inside an organization (org_id). The new display starts offline. For a physical screen ALWAYS prefer pair_by_code, which creates and pairs in one step; use create_display only to prepare a display before the screen exists or for virtual/API-o...
This record as markdown: /tools/de-agentview-agentview-mcp/create-display.md
What create_display does on agentView
AI agents use create_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 |
|---|---|---|---|
name | string | — | Friendly display name, e.g. 'Lobby Screen'. Required when org_id is set. |
org_id | string | — | Optional: create the display inside this organization (needs manager role and a free license slot). |
access_token | string | — | Optional bearer token; prefer session_request_id. |
session_request_id | string | — | Session handle from create_auth_session; pass it on every authenticated call. |
Parameters from the server's own tool schema.
Why create_display is rated Medium
An AI agent can call create_display faster than any human can review: one bad instruction and it creates or modifies resources in agentView by the hundred, each call as confident as the last.
Risk signalsHandles credentials or secrets (access_token) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs create_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 create_display, this is the rule to start with:
create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect agentView, apply this rule, and every create_display call is checked against it from then on.
Questions about create_display
Pre-provisions a display without hardware, personal or inside an organization (org_id). The new display starts offline. For a physical screen ALWAYS prefer pair_by_code, which creates and pairs in one step; use create_display only to prepare a display before the screen exists or for virtual/API-only displays. Requires admin scope. Returns id plus setup and pairing URLs. 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.
create_display accepts 4 parameters: name, org_id, access_token, session_request_id. The full parameter table on this page comes from the server's own tool schema.
Register the agentView MCP server in PolicyLayer and add a rule for create_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.
create_display 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_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
More on agentView, and thousands of servers like it.
This server
Across the catalogue