list-tenants

THE RISK

Low Risk

Why list-tenants needs a policy

This tool performs a read-only operation that lists Azure tenants. It has no side effects, does not modify data, execute code, or trigger external operations. The blast radius is minimal—it only exposes metadata about available tenants that an authenticated user can already access. Severity is low because listing tenants is informational and does not enable unauthorized actions by itself.

From the tool's definition Tool name 'list-tenants' and description 'List all available Azure tenants' indicate a query operation that retrieves information without modifying any data.

Documented attack patterns abuse exactly the kind of access list-tenants gives an agent:

POLICY

How to control list-tenants

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-tenants:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list-tenants": {}
  }
}

list-tenants 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-role-definitions List available role definitions 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

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 list-tenants

What does the list-tenants tool do? +

List all available Azure tenants. 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 list-tenants? +

Register the Azure MCP Server MCP server in PolicyLayer and add a rule for list-tenants: 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 list-tenants? +

list-tenants is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list-tenants? +

Yes. Add a rate_limit block to the list-tenants 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 list-tenants completely? +

Set action: deny in the PolicyLayer policy for list-tenants. 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 list-tenants? +

list-tenants 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 →