Peek (without consuming) up to max_count messages on a queue.
AI agents call servicebus_peek 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 retrieves message metadata from a Service Bus queue without consuming (removing) or modifying messages. It has no side effects and does not commit the messages for processing. This is a classic read operation—inspecting data to determine its state without changing it. Severity is low because the blast radius of misuse is limited to information disclosure.
From the tool's definition Tool description states 'Peek (without consuming)' messages, which is a non-destructive inspection operation. The word 'peek' indicates read-only access without side effects or message removal.
Attacks that exploit this kind of access
Peek (without consuming) up to max_count messages on a queue. 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 servicebus_peek: 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.
servicebus_peek 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 servicebus_peek 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 servicebus_peek. 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.
servicebus_peek 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 →