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.
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.
Converting an owner team to an access team is an irreversible structural change to the authorization and ownership model. Once converted, the previous ownership semantics cannot be restored without manual intervention, and it directly impacts record management permissions across potentially many records. This meets the Destructive criterion of irreversible state change with broad implications.
From the tool's definition Tool description explicitly states 'This action cannot be undone' and 'affects how records owned by this team are managed.' The conversion irreversibly transforms team ownership semantics.
Documented attack patterns abuse exactly the kind of access convert_owner_team_to_access_team gives an agent:
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 convert_owner_team_to_access_team:
{
"version": "1",
"default": "deny",
"hide": [
"convert_owner_team_to_access_team"
]
}convert_owner_team_to_access_team disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
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.
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.
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.
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.
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.
convert_owner_team_to_access_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.
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.
Free to start. No card required.
71 Dataverse MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.