Send a text message to a Service Bus queue.
AI agents invoke servicebus_send to trigger actions in Mcp Azure Toolkit. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Sending a message to a Service Bus queue is an external operation that triggers downstream consumers and workflows. It is not a simple data write within a contained system; it dispatches events or commands to other services. This fits Execute as it triggers external operations whose effects depend on the message content and recipients.
From the tool's definition 'Send a text message to a Service Bus queue' — triggers an external messaging operation that dispatches a message to an external system
Attacks that exploit this kind of access
Send a text message to a Service Bus queue. It is categorised as a Execute tool in the Mcp Azure Toolkit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Azure Toolkit MCP server in PolicyLayer and add a rule for servicebus_send: 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_send is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the servicebus_send 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_send. 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_send 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 →