delete_display
Permanently deletes a display and all its associated content. This action cannot be undone. Use this only when the user explicitly confirms they want to remove the display. Requires admin scope. Returns id, name and deleted (boolean true).
This record as markdown: /tools/de-agentview-agentview-mcp/delete-display.md
What delete_display does on agentView
AI agents call delete_display to permanently remove resources in agentView, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
display_id | string | Yes | The 8-character alphanumeric display profile ID to delete, e.g. 'ABCD1234'. |
access_token | string | — | Optional bearer token; prefer session_request_id. |
Parameters from the server's own tool schema.
Why delete_display is rated Critical
The tool irreversibly deletes data (display and associated content) with no undo capability. This matches the Destructive category definition. Severity is high because deletion impacts infrastructure/configuration, requires admin scope, and affects multiple entities (display plus all associated content), though the blast radius is somewhat limited to a single display rather than organization-wide data.
From the tool's definition Permanently deletes a display and all its associated content. This action cannot be undone.
Risk signalsHandles credentials or secrets (access_token) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs delete_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 delete_display, this is the rule to start with:
delete_display is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect agentView, apply this rule, and every delete_display call is checked against it from then on.
Questions about delete_display
Permanently deletes a display and all its associated content. This action cannot be undone. Use this only when the user explicitly confirms they want to remove the display. Requires admin scope. Returns id, name and deleted (boolean true). It is categorised as a Destructive tool in the agentView MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_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.
Register the agentView MCP server in PolicyLayer and add a rule for delete_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.
delete_display is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue