connect
Connect to Redis instance. Can use REDIS_URL environment variable if set. When running in Docker, localhost will automatically redirect to host.docker.internal.
This record as markdown: /tools/adamhancock-bullmq-mcp/connect.md
What connect does on BullMQ MCP Server
AI agents use connect to create or update resources in BullMQ MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BullMQ MCP Server environment.
Why connect is rated Medium
While a connection itself is not immediately destructive or financial, establishing a Redis connection in the context of a queue management system is a state-changing Write operation. The connection can be reversed via the 'disconnect' tool (a sibling).
From the tool's definition The tool description states 'Connect to Redis instance' which establishes a connection state that modifies the client's configuration and internal connection registry.
Attacks that exploit this kind of access
The rule that runs connect 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 connect, this is the rule to start with:
connect stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 connect call is checked against it from then on.
Questions about connect
Connect to Redis instance. Can use REDIS_URL environment variable if set. When running in Docker, localhost will automatically redirect to host.docker.internal. It is categorised as a Write tool in the BullMQ MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the BullMQ MCP Server MCP server in PolicyLayer and add a rule for connect: 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.
connect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the connect 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 connect. 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.
connect 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