delete_web_resource
AI agents call delete_web_resource 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.
The 'delete' prefix places this squarely in the Destructive category. Web resources are integral parts of Dataverse solutions; deleting them permanently removes functionality and configuration. While the description is empty (reducing confidence slightly), the tool name alone is sufficiently explicit.
From the tool's definition Tool name is 'delete_web_resource' — the verb 'delete' indicates irreversible removal of data. Web resources in Dataverse are solution artifacts (scripts, HTML, CSS, images) that once deleted cannot be recovered without restoration from backup.
Attacks that exploit this kind of access
delete_web_resource. 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 delete_web_resource: 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.
delete_web_resource 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_web_resource 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_web_resource. 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_web_resource is provided by the Dataverse MCP Server MCP server (wizspdemo/dataverse-mcp3). 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 →