Retrieves a list of security roles in the Dataverse environment with filtering options. Use this to discover available roles, find custom roles, or get an overview of permission structures. Supports filtering by business unit, custom/system roles, and managed/unmanaged status.
AI agents call list_dataverse_roles to retrieve information from Dataverse MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves role metadata from Dataverse without modifying, executing, or destroying any data. It is a read-only discovery operation used to inspect the existing security role structure. While the information retrieved could be sensitive in some contexts, the tool itself poses minimal risk as it merely returns existing configuration data without altering state or triggering external actions.
From the tool's definition Tool name contains 'list' and description states 'Retrieves a list of security roles' with 'filtering options' to 'discover available roles' and 'get an overview' — purely informational operations with no modifications, deletions, or side effects.
Attacks that exploit this kind of access
Retrieves a list of security roles in the Dataverse environment with filtering options. Use this to discover available roles, find custom roles, or get an overview of permission structures. Supports filtering by business unit, custom/system roles, and managed/unmanaged status. It is categorised as a Read tool in the Dataverse MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dataverse MCP Server MCP server in PolicyLayer and add a rule for list_dataverse_roles: 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.
list_dataverse_roles is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_dataverse_roles 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 list_dataverse_roles. 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.
list_dataverse_roles 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.
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 →