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 returns security role information without creating, modifying, deleting, or executing any actions. It is a safe reconnaissance operation that an AI agent could perform to understand the access control landscape but cannot cause harm on its own. The filtering capabilities are read-time parameters, not side-effect-producing operations.
From the tool's definition Tool name contains 'list' and description states 'Retrieves a list' and 'discover available roles' — purely a query operation with no modification or execution. Filtering options are applied to the read operation itself.
Documented attack patterns abuse exactly the kind of access list_dataverse_roles 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 list_dataverse_roles:
{
"version": "1",
"default": "deny",
"tools": {
"list_dataverse_roles": {}
}
}list_dataverse_roles is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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 (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.