Creates a new team in Dataverse for organizing users and managing permissions. Teams can be owner teams (for record ownership) or access teams (for sharing records). Use this to establish groups of users who work together and need similar access levels.
AI agents use create_dataverse_team to create or update resources in Dataverse MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dataverse MCP Server environment.
This tool creates new security/organizational structures (teams) in a Dataverse environment, which is a reversible data modification operation. It modifies the directory/configuration state by adding a new principal (team) to the system. While it creates users/principals that could potentially be misused for privilege escalation, the tool itself is fundamentally a Write operation since team creation can be undone.
From the tool's definition Creates a new team in Dataverse for organizing users and managing permissions. Teams can be owner teams (for record ownership) or access teams (for sharing records).
Attacks that exploit this kind of access
Creates a new team in Dataverse for organizing users and managing permissions. Teams can be owner teams (for record ownership) or access teams (for sharing records). Use this to establish groups of users who work together and need similar access levels. It is categorised as a Write tool in the Dataverse MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dataverse MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_dataverse_team is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_dataverse_team is provided by the Dataverse MCP Server MCP server (wizspdemo/dataverse-mcp2). 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 →