AI agents call get-channel to retrieve information from Rabbitmq without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes |
Parameters from the server's own tool schema.
This tool retrieves channel metadata/state from RabbitMQ without modifying, deleting, or executing operations. The verb 'get' and use case (inspecting channel details) are characteristic of Read category tools. The low severity reflects minimal blast radius—an agent querying channel information cannot cause operational damage.
From the tool's definition Tool name 'get-channel' and description 'Get details for a specific channel' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get details for a specific channel. It is categorised as a Read tool in the Rabbitmq MCP Server, which means it retrieves data without modifying state.
get-channel accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Rabbitmq MCP server in PolicyLayer and add a rule for get-channel: 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 Rabbitmq. Nothing to install.
get-channel 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 get-channel 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 get-channel. 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.
get-channel is provided by the Rabbitmq MCP server (rabbitmq-mcp). 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 →