delete_row
AI agents call delete_row to permanently remove resources in DataBeak — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the description is empty, the function name 'delete_row' in the context of a CSV data manipulation tool clearly indicates irreversible deletion of data. Given the tool's position among transformation tools (add_column, filter_rows, fill_missing_values), it logically represents a destructive row removal operation.
From the tool's definition Tool name 'delete_row' combined with sibling tools that perform read and write operations on CSV data indicates this tool irreversibly removes rows from datasets. The 'delete' prefix matches the Destructive category definition of irreversible data removal.
Attacks that exploit this kind of access
delete_row. It is categorised as a Destructive tool in the DataBeak MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the DataBeak MCP server in PolicyLayer and add a rule for delete_row: 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 DataBeak. Nothing to install.
delete_row 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_row 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_row. 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_row is provided by the DataBeak MCP server (jonpspri/databeak). 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 →