# delete_report

Remove a report from its table and from every portal menu that shows it. The table and its records stay. Cannot be undone. Ids come from get_reports.

Agent View of the PolicyLayer registry record for `delete_report`. HTML page: https://policylayer.com/tools/com-quintadb-mcp/delete-report

## Facts

- Tool: `delete_report`
- Server: QuintaDB (`https://quintadb.com/mcp`) — https://policylayer.com/tools/com-quintadb-mcp.md
- Homepage: https://github.com/https://quintadb.com/mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2 (2 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `app_id` | string | yes | Project ID (from list_projects) |
| `report_id` | string | yes | View/filter ID (from get_reports) |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "delete_report",
    "arguments": {
      "app_id": "<app_id>",
      "report_id": "<report_id>"
    }
  }
}
```

## Why delete_report is rated Critical

An AI agent that decides to call delete_report doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from QuintaDB is gone. There is no undo for destructive operations.

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents call delete_report to permanently remove resources in QuintaDB, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches QuintaDB:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_report"
  ]
}
```

## Other tools on QuintaDB (149)

- `delete_action_rule` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-action-rule.md
- `delete_calendar` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-calendar.md
- `delete_chart` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-chart.md
- `delete_dashboard_item` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-dashboard-item.md
- `delete_few_records` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-few-records.md
- `delete_field` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-field.md
- `delete_form` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-form.md
- `delete_formatting` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-formatting.md
- `delete_map` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-map.md
- `delete_portal` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-portal.md
- `delete_portal_group` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-portal-group.md
- `delete_portal_menu_item` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-portal-menu-item.md
- `delete_portal_page` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-portal-page.md
- `delete_portal_user` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-portal-user.md
- `delete_project` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-project.md
- `delete_record` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-record.md
- `delete_records_by_filter` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-records-by-filter.md
- `delete_reminder` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-reminder.md
- `delete_saved_view` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-saved-view.md
- `delete_schedule` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-schedule.md
- `delete_team_group` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-team-group.md
- `delete_template` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-template.md
- `delete_webhook` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-webhook.md
- `remove_example_records` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/remove-example-records.md
- `remove_user_from_portal_group` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/remove-user-from-portal-group.md
- `remove_user_from_team_group` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/remove-user-from-team-group.md
- `run_action` — Execute — https://policylayer.com/tools/com-quintadb-mcp/run-action.md
- `check_ai_site_status` — Read — https://policylayer.com/tools/com-quintadb-mcp/check-ai-site-status.md
- `describe_project` — Read — https://policylayer.com/tools/com-quintadb-mcp/describe-project.md
- `export_records` — Read — https://policylayer.com/tools/com-quintadb-mcp/export-records.md
- …and 119 more: https://policylayer.com/tools/com-quintadb-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-quintadb-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-quintadb-mcp