List all available Bull queues in LaunchFrame with their purpose and usage rules.
AI agents call queue_get_names to retrieve information from LaunchFrame MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves informational data about existing Bull queues (names, purposes, usage rules) with no side effects. It is a read-only query operation similar to 'get' or 'list' operations. The low severity reflects that exposing queue names and their purposes poses minimal risk—an agent cannot harm systems by merely reading this architectural metadata.
From the tool's definition Tool name 'queue_get_names' and description 'List all available Bull queues' indicate a retrieval operation that queries queue metadata without modifying state.
Attacks that exploit this kind of access
List all available Bull queues in LaunchFrame with their purpose and usage rules. It is categorised as a Read tool in the LaunchFrame MCP MCP Server, which means it retrieves data without modifying state.
Register the LaunchFrame MCP server in PolicyLayer and add a rule for queue_get_names: 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 LaunchFrame MCP. Nothing to install.
queue_get_names 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 queue_get_names 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 queue_get_names. 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.
queue_get_names is provided by the LaunchFrame MCP server (launchframe-dev/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 →