delete_data_slot
Permanently deletes a data slot. Display HTML fetching its readUrl will receive 404 after deletion. Cannot be undone. Supply group_id to delete a group slot; omit for personal slots. Requires authentication.
This record as markdown: /tools/de-agentview-agentview-mcp/delete-data-slot.md
What delete_data_slot does on agentView
AI agents call delete_data_slot 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 |
|---|---|---|---|
slug | string | Yes | The slug of the data slot to delete. |
group_id | string | — | Group/organization ID to delete a group slot. Omit for personal slots. |
access_token | string | — | Optional bearer token; prefer session_request_id. |
Parameters from the server's own tool schema.
Why delete_data_slot is rated Critical
An AI agent that decides to call delete_data_slot doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from agentView is gone. There is no undo for destructive operations.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs delete_data_slot 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_data_slot, this is the rule to start with:
delete_data_slot 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_data_slot call is checked against it from then on.
Questions about delete_data_slot
Permanently deletes a data slot. Display HTML fetching its readUrl will receive 404 after deletion. Cannot be undone. Supply group_id to delete a group slot; omit for personal slots. Requires authentication. 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_data_slot accepts 3 parameters: slug, group_id, access_token. Required: slug. 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_data_slot: 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_data_slot 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_data_slot 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_data_slot. 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_data_slot 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