get-role-definitions

THE RISK

Low Risk

Why get-role-definitions needs a policy

This tool retrieves and lists role definitions without creating, modifying, deleting, or executing operations. It is informational in nature and has no side effects. The blast radius of misuse is minimal—an agent querying role definitions cannot cause damage or unauthorized changes to Azure resources.

From the tool's definition Tool name is 'get-role-definitions' and description states 'List available role definitions' — a read-only retrieval operation with no modification or execution.

Documented attack patterns abuse exactly the kind of access get-role-definitions gives an agent:

POLICY

How to control get-role-definitions

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 get-role-definitions:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-role-definitions": {}
  }
}

get-role-definitions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Azure MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Azure MCP Server tools

Execute run-azure-code Run Azure code Write create-resource-group Create a new resource group Write select-tenant Select Azure tenant and subscription Read get-resource-details Get detailed information about a specific resource Read get-user-permissions Get detailed user permissions by combining role assignments and role definitions Read list-resource-groups List all resource groups in the selected subscription Read list-role-assignments List role assignments for the subscription or resource group Read list-tenants List all available Azure tenants

All 9 Azure MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get-role-definitions

What does the get-role-definitions tool do? +

List available role definitions. It is categorised as a Read tool in the Azure MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-role-definitions? +

Register the Azure MCP Server MCP server in PolicyLayer and add a rule for get-role-definitions: 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.

What risk level is get-role-definitions? +

get-role-definitions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-role-definitions? +

Yes. Add a rate_limit block to the get-role-definitions 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.

How do I block get-role-definitions completely? +

Set action: deny in the PolicyLayer policy for get-role-definitions. 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.

What MCP server provides get-role-definitions? +

get-role-definitions 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.

Enforce policy on every Azure MCP Server tool call.

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.

CHECK YOUR STACK →