convert_owner_team_to_access_team

Converts an owner team to an access team, changing how the team can be used for record ownership and sharing. WARNING: This action cannot be undone and affects how records owned by this team are managed.

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

What convert_owner_team_to_access_team does on Dataverse MCP Server

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

Although the tool does not delete data, it irreversibly transforms a fundamental organizational structure (team type) that affects record ownership and sharing semantics. This transformation cannot be reverted and has cascading effects on how records are managed throughout the system.

From the tool's definition Tool description explicitly states 'WARNING: This action cannot be undone' and 'Converts an owner team to an access team, changing how the team can be used for record ownership and sharing.' The irreversible nature of the conversion and its impact on record…

Questions about convert_owner_team_to_access_team

What does the convert_owner_team_to_access_team tool do? +

Converts an owner team to an access team, changing how the team can be used for record ownership and sharing. WARNING: This action cannot be undone and affects how records owned by this team are managed. 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 convert_owner_team_to_access_team? +

Register the Dataverse MCP Server MCP server in PolicyLayer and add a rule for convert_owner_team_to_access_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 convert_owner_team_to_access_team? +

convert_owner_team_to_access_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 convert_owner_team_to_access_team? +

Yes. Add a rate_limit block to the convert_owner_team_to_access_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 convert_owner_team_to_access_team completely? +

Set action: deny in the PolicyLayer policy for convert_owner_team_to_access_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 convert_owner_team_to_access_team? +

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