delete_asset
Deletes one or more assets. Displays referencing deleted assets will show broken images. Requires authentication with at least content_only scope.
This record as markdown: /tools/de-agentview-agentview-mcp/delete-asset.md
What delete_asset does on agentView
AI agents call delete_asset 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 |
|---|---|---|---|
asset_ids | array | Yes | One or more asset IDs to delete. |
access_token | string | — | Optional bearer token; prefer session_request_id. |
Parameters from the server's own tool schema.
Why delete_asset is rated Critical
The tool performs irreversible deletion of assets, which is the defining characteristic of the Destructive category. Once deleted, the assets cannot be recovered and dependent displays will break. This represents high severity because multiple displays could be affected simultaneously, creating a significant blast radius if an AI agent misuses this tool by deleting assets it should not have.
From the tool's definition Tool name is 'delete_asset' and description explicitly states 'Deletes one or more assets' with the irreversible consequence that 'Displays referencing deleted assets will show broken images.' This is a permanent deletion operation.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs delete_asset 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_asset, this is the rule to start with:
delete_asset 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_asset call is checked against it from then on.
Questions about delete_asset
Deletes one or more assets. Displays referencing deleted assets will show broken images. Requires authentication with at least content_only 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_asset accepts 2 parameters: asset_ids, access_token. Required: asset_ids. 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_asset: 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_asset 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_asset 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_asset. 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_asset 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