// MCP TOOL REFERENCE

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.

ServerDataverse MCP Server
CategoryDestructive

How to control delete_dataverse_team ↓

WHAT IT DOES

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.

THE RISK

Critical Risk

Why delete_dataverse_team needs a policy

This tool irreversibly deletes data (a team object) from the Dataverse system. While the operation has safeguards (fails if team owns records or has roles), the core function is permanent deletion with no undo capability, making it Destructive rather than Write.

From the tool's definition Tool description explicitly states "Permanently deletes a team from Dataverse" and "This action cannot be undone". The irreversibility and permanent deletion nature directly matches the Destructive category definition.

Documented attack patterns abuse exactly the kind of access delete_dataverse_team gives an agent:

POLICY

How to control delete_dataverse_team

PolicyLayer is an MCP gateway — it sits between your AI agents and Dataverse MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_dataverse_team:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_dataverse_team"
  ]
}

delete_dataverse_team disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Dataverse MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Dataverse MCP Server tools

Destructive convert_owner_team_to_access_team Converts an owner team to an access team, changing how the team can be used for record own Destructive delete_dataverse_businessunit Permanently deletes a business unit from Dataverse. WARNING: This action cannot be undone Destructive delete_dataverse_column Permanently deletes a column from a Dataverse table. WARNING: This action cannot be undone Destructive delete_dataverse_optionset Permanently deletes an option set from Dataverse. WARNING: This action cannot be undone an Destructive delete_dataverse_relationship Permanently deletes a relationship between Dataverse tables. WARNING: This action cannot b Destructive delete_dataverse_role Permanently deletes a security role from Dataverse. WARNING: This action cannot be undone Destructive delete_dataverse_table Permanently deletes a custom table from Dataverse. WARNING: This action cannot be undone a Destructive remove_members_from_team Removes users from team membership, revoking their access to team-owned records and team-b

All 71 Dataverse MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Dataverse MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

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 (mwhesse/dataverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Dataverse MCP Server tool call.

Start from Dataverse MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

71 Dataverse MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.