delete_organization
Permanently deletes an organization, releasing all its displays and removing all members. Only the owner can delete. This cannot be undone. Requires admin scope.
This record as markdown: /tools/de-agentview-agentview-mcp/delete-organization.md
What delete_organization does on agentView
AI agents call delete_organization 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 to delete. |
access_token | string | — | Optional bearer token; prefer session_request_id. |
Parameters from the server's own tool schema.
Why delete_organization is rated Critical
This tool irreversibly deletes an entire organization and all associated resources (displays, members). The operation cannot be undone and affects multiple entities. While it requires admin scope, misuse by a compromised admin account or social engineering could result in complete loss of organizational infrastructure and user access.
From the tool's definition Tool description explicitly states: "Permanently deletes an organization", "releasing all its displays", "cannot be undone", and "Requires admin scope".
Risk signalsHandles credentials or secrets (access_token) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs delete_organization 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_organization, this is the rule to start with:
delete_organization 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_organization call is checked against it from then on.
Questions about delete_organization
Permanently deletes an organization, releasing all its displays and removing all members. Only the owner can delete. This cannot be undone. Requires admin scope. 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_organization accepts 2 parameters: org_id, access_token. Required: org_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_organization: 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_organization 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_organization 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_organization. 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_organization 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