This record as markdown: /tools/adamhancock-bullmq-mcp/list-connections.md
What list_connections does on BullMQ MCP Server
AI agents call list_connections to retrieve information from BullMQ MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_connections is rated Low
This tool queries existing connection metadata but does not create, modify, delete, or execute any operations. It is purely informational, making it a Read category risk. Severity is low because connection metadata alone does not expose sensitive data like credentials or enable direct system access; it only lists connection identifiers or configurations already known to the user.
From the tool's definition Tool name is 'list_connections' and description states 'List all saved connections' — this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_connections safely
PolicyLayer is an MCP gateway: it sits between your AI agents and BullMQ MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_connections, this is the rule to start with:
list_connections is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect BullMQ MCP Server, apply this rule, and every list_connections call is checked against it from then on.
Questions about list_connections
List all saved connections. It is categorised as a Read tool in the BullMQ MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BullMQ MCP Server MCP server in PolicyLayer and add a rule for list_connections: 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 BullMQ MCP Server. Nothing to install.
list_connections 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_connections 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_connections. 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_connections is provided by the BullMQ MCP Server MCP server (adamhancock/bullmq-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on BullMQ MCP Server, and thousands of servers like it.
This server
Across the catalogue