dataverse_delete_record
Delete a record from a Dataverse table
This record as markdown: /tools/ajscheuer-dataverse-mcp/dataverse-delete-record.md
What dataverse_delete_record does on Dataverse MCP Server
AI agents call dataverse_delete_record to permanently remove resources in Dataverse MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why dataverse_delete_record is rated Critical
Deletion of database records cannot be undone and represents permanent data loss. This is the defining characteristic of the Destructive category. Severity is high rather than critical because the blast radius depends on which record is targeted, but unauthorized deletion of production data could cause significant business impact.
From the tool's definition Tool name 'dataverse_delete_record' and description 'Delete a record from a Dataverse table' explicitly perform irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs dataverse_delete_record safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dataverse MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dataverse_delete_record, this is the rule to start with:
dataverse_delete_record is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Dataverse MCP Server, apply this rule, and every dataverse_delete_record call is checked against it from then on.
Questions about dataverse_delete_record
Delete a record from a Dataverse table. It is categorised as a Destructive tool in the Dataverse MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Dataverse MCP Server MCP server in PolicyLayer and add a rule for dataverse_delete_record: 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 Dataverse MCP Server. Nothing to install.
dataverse_delete_record 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 dataverse_delete_record 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 dataverse_delete_record. 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.
dataverse_delete_record is provided by the Dataverse MCP Server MCP server (ajscheuer/dataverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dataverse MCP Server, and thousands of servers like it.
Across the catalogue