Delete a field from a table
AI agents call quickbase_delete_field 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 field from a table is a destructive operation that cannot be undone and will permanently remove the field and any associated data. This impacts data structure and integrity across the system. While not directly financial, it has high blast radius if executed against the wrong field or table, potentially causing data loss or application failure.
From the tool's definition Tool name explicitly states 'delete_field' and description confirms 'Delete a field from a table'. This is an irreversible deletion operation that removes structured data schema elements.
Attacks that exploit this kind of access
Delete a field from a table. 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_field: 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_field 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_field 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_field. 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_field 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 →