delete_dataverse_team

Permanently deletes a team from Dataverse. WARNING: This action cannot be undone and will fail if the team owns records or has assigned security roles. Ensure the team is not in use before deletion.

Server Dataverse MCP Server wizspdemo/dataverse-mcp3
Category Destructive
Risk class Critical
Parameters 00 required

What delete_dataverse_team does on Dataverse MCP Server

AI agents call delete_dataverse_team 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 delete_dataverse_team needs a policy

The tool irreversibly deletes a team entity from Dataverse, which is the defining characteristic of the Destructive category. The description explicitly states this action 'cannot be undone,' indicating permanent data loss. While it has preconditions (team must not own records or have security roles), the operation itself is destructive in nature.

From the tool's definition Permanently deletes a team from Dataverse. WARNING: This action cannot be undone

Questions about delete_dataverse_team

What does the delete_dataverse_team tool do? +

Permanently deletes a team from Dataverse. WARNING: This action cannot be undone and will fail if the team owns records or has assigned security roles. Ensure the team is not in use before deletion. 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.

How do I enforce a policy on delete_dataverse_team? +

Register the Dataverse MCP Server MCP server in PolicyLayer and add a rule for delete_dataverse_team: 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.

What risk level is delete_dataverse_team? +

delete_dataverse_team is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_dataverse_team? +

Yes. Add a rate_limit block to the delete_dataverse_team 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.

How do I block delete_dataverse_team completely? +

Set action: deny in the PolicyLayer policy for delete_dataverse_team. 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.

What MCP server provides delete_dataverse_team? +

delete_dataverse_team 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.