List the blob containers in the storage account.
AI agents call blob_list_containers to retrieve information from Mcp Azure Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query/list operation on Azure Blob Storage to enumerate containers. It retrieves metadata without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an attacker gains visibility into container names but cannot access their contents without additional permissions or tools (e.g., blob_read). This is clearly a Read category tool.
From the tool's definition Tool name 'blob_list_containers' and description 'List the blob containers in the storage account' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List the blob containers in the storage account. It is categorised as a Read tool in the Mcp Azure Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Mcp Azure Toolkit MCP server in PolicyLayer and add a rule for blob_list_containers: 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 Mcp Azure Toolkit. Nothing to install.
blob_list_containers 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 blob_list_containers 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 blob_list_containers. 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.
blob_list_containers is provided by the Mcp Azure Toolkit MCP server (temidireadesiji/mcp-azure-toolkit). 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 →