remove_csv_row
AI agents call remove_csv_row to permanently remove resources in Restcsv — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a CSV row is a destructive operation that cannot be undone—it permanently deletes data. This warrants Destructive category rather than Write (which is reversible). Severity is high because bulk row deletion could affect significant data sets, though impact depends on the CSV's size and importance.
From the tool's definition Tool name 'remove_csv_row' indicates deletion of data row(s) from CSV storage. Sibling tools include 'delete_csv' and 'delete_action', establishing a pattern of destructive operations on this server. The action is irreversible row deletion.
Attacks that exploit this kind of access
remove_csv_row. It is categorised as a Destructive tool in the Restcsv MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Restcsv MCP server in PolicyLayer and add a rule for remove_csv_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 Restcsv. Nothing to install.
remove_csv_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 remove_csv_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 remove_csv_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.
remove_csv_row is provided by the Restcsv MCP server (restcsv-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 →