Creates a new security role in Dataverse to define permissions and access levels for users and teams. Security roles control what users can see and do within the system. Use this to establish custom permission sets for different user types or job functions.
AI agents use create_dataverse_role 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 role entities in Dataverse, which is a reversible write operation (roles can be deleted or modified). While it affects security permissions, it does not execute arbitrary code, delete data, or move money. The severity is high because misconfigured roles could grant excessive permissions to users, but the operation itself is not irreversible (roles can be removed).
From the tool's definition Tool description states it "Creates a new security role" in Dataverse, which is a write operation that modifies the system configuration by adding a new entity.
Attacks that exploit this kind of access
Creates a new security role in Dataverse to define permissions and access levels for users and teams. Security roles control what users can see and do within the system. Use this to establish custom permission sets for different user types or job functions. 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_role: 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_role 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_role 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_role. 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_role 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.
create_dataverse_role is one line of Dataverse MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →