List role assignments for the subscription or resource group
AI agents call list-role-assignments to retrieve information from Azure 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 role assignment information without modifying, deleting, or executing operations. The 'list' action is a read-only operation that retrieves data for visibility and auditing purposes. No side effects occur on the system state.
From the tool's definition Tool name 'list-role-assignments' and description 'List role assignments' indicate retrieval of existing role assignment data with no modification or deletion.
Documented attack patterns abuse exactly the kind of access list-role-assignments gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Azure MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list-role-assignments:
{
"version": "1",
"default": "deny",
"tools": {
"list-role-assignments": {}
}
} list-role-assignments 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.
List role assignments for the subscription or resource group. It is categorised as a Read tool in the Azure MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure MCP Server MCP server in PolicyLayer and add a rule for list-role-assignments: 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 Azure MCP Server. Nothing to install.
list-role-assignments 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-role-assignments 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-role-assignments. 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-role-assignments is provided by the Azure MCP Server MCP server (kalivaraprasad-gonapa/azure-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Azure 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.
9 Azure MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.