AI agents call list-auth-attempts-node 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 |
|---|---|---|---|
node | string | Yes |
Parameters from the server's own tool schema.
This tool queries and retrieves historical authentication attempt data without modifying state, executing code, or triggering side effects. It is a straightforward read operation on audit/log data maintained by RabbitMQ.
From the tool's definition Tool name contains 'list' and description states 'List all authentication attempts for a node' — a pure retrieval operation with no mutation or execution of external commands.
Attacks that exploit this kind of access
List all authentication attempts for a node. It is categorised as a Read tool in the Rabbitmq MCP Server, which means it retrieves data without modifying state.
list-auth-attempts-node accepts 1 parameter: node. Required: node. 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 list-auth-attempts-node: 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.
list-auth-attempts-node 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 list-auth-attempts-node 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 list-auth-attempts-node. 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.
list-auth-attempts-node 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 →