create_org_display

SERVERagentView SOURCEhttps://agentview.de/mcp

Medium RISK CLASS

Category Write

Parameters 32 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/create-org-display.md

WHAT IT DOES

What create_org_display does on agentView

AI agents use create_org_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	Yes	Friendly name for the new display. Example: 'Lobby Screen'.
`org_id`	string	Yes	The organization ID to create the display in. Obtain this from list_organizations.
`access_token`	string	—	Optional JWT access token for authentication.

Parameters from the server's own tool schema.

RISK

Why create_org_display is rated Medium

This tool creates new organizational resources (displays) in a reversible manner. It modifies the organization's display inventory by adding a new entry, but the action is not destructive—displays can be deleted or reconfigured. It requires administrative privileges and license availability, limiting blast radius to authenticated admins.

From the tool's definition Creates a new display directly within an organization WITHOUT pairing it to physical hardware. The display starts offline and uncoupled... owned by the organization, not by a personal user.

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_org_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_org_display, this is the rule to start with:

create_org_display Rate-limited

create_org_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": {
    "create_org_display": {
      "limits": [
        {
          "counter": "create_org_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 create_org_display call is checked against it from then on.

FAQ

Questions about create_org_display

What does the create_org_display tool do? +

Creates a new display directly within an organization WITHOUT pairing it to physical hardware. The display starts offline and uncoupled. For physical screens, ALWAYS prefer pair_by_code instead — it creates and pairs in one step. Use create_org_display only for administrative pre-provisioning when the screen is not yet available. The display is owned by the organization, not by a personal user. Requires admin scope and manager or higher role in the organization. The organization must have available licenses (use allocate_licenses first if needed). 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 create_org_display accept? +

create_org_display accepts 3 parameters: name, org_id, access_token. Required: name, org_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_org_display? +

Register the agentView MCP server in PolicyLayer and add a rule for create_org_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 create_org_display? +

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

Can I rate-limit create_org_display? +

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

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

create_org_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

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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