Delete a table from QuickBase
AI agents call quickbase_delete_table to permanently remove resources in QuickBase MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a table irreversibly removes all associated data, fields, relationships, and records stored within it. This action cannot be undone and represents complete data loss for that table. While not financial in nature, it is destructive and warrants the highest non-critical severity due to the bounded scope (single table rather than entire database).
From the tool's definition Tool name is 'quickbase_delete_table' and description states 'Delete a table from QuickBase'. The verb 'delete' combined with the scope 'table' indicates irreversible removal of data and schema.
Attacks that exploit this kind of access
Delete a table from QuickBase. It is categorised as a Destructive tool in the QuickBase MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the QuickBase MCP Server MCP server in PolicyLayer and add a rule for quickbase_delete_table: 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 QuickBase MCP Server. Nothing to install.
quickbase_delete_table 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 quickbase_delete_table 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 quickbase_delete_table. 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.
quickbase_delete_table is provided by the QuickBase MCP Server MCP server (lawrencecirillo/quickbase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →