remove_display_from_org
Removes a display from an organization, clearing its group assignment and all display grants. The display becomes unassigned. Requires admin scope and admin or owner role.
This record as markdown: /tools/de-agentview-agentview-mcp/remove-display-from-org.md
What remove_display_from_org does on agentView
AI agents call remove_display_from_org 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 |
|---|---|---|---|
org_id | string | Yes | The organization ID. |
display_id | string | Yes | The display profile ID to remove. |
access_token | string | — | Optional bearer token; prefer session_request_id. |
Parameters from the server's own tool schema.
Why remove_display_from_org is rated Critical
This tool irreversibly modifies the organizational structure and access control of a display. While the display itself may not be deleted, its organizational assignment and associated grants are permanently removed and would require re-configuration to restore. This represents a destructive action on organizational state that cannot be easily undone.
From the tool's definition Tool removes a display from an organization by clearing its group assignment and all display grants. This is an irreversible operation that severs the display's organizational bindings and access permissions.
Risk signalsHandles credentials or secrets (access_token) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs remove_display_from_org 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 remove_display_from_org, this is the rule to start with:
remove_display_from_org 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 remove_display_from_org call is checked against it from then on.
Questions about remove_display_from_org
Removes a display from an organization, clearing its group assignment and all display grants. The display becomes unassigned. Requires admin scope and admin or owner role. 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.
remove_display_from_org accepts 3 parameters: org_id, display_id, access_token. Required: org_id, 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 remove_display_from_org: 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.
remove_display_from_org 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 remove_display_from_org 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 remove_display_from_org. 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.
remove_display_from_org 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