Searches for routing queues based on their name, allowing for wildcard searches. Returns a paginated list of matching queues, including their Name, ID, Description (if available), and Member Count (if available). Also provides pagination details like current page, page size, total results found, ...
AI agents call search_queues to retrieve information from Genesys Cloud MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves queue information from Genesys Cloud without creating, modifying, deleting, or executing any operations. It performs a read-only lookup with pagination, similar to a search or list operation. The blast radius of misuse is minimal—worst case, an agent queries queues it shouldn't have visibility into, but no data is altered or financial impact occurs.
From the tool's definition Tool description states it 'Searches for routing queues' and 'Returns a paginated list of matching queues' with metadata like Name, ID, Description, and Member Count. The verb 'search' and 'returns' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access search_queues gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Genesys Cloud MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_queues:
{
"version": "1",
"default": "deny",
"tools": {
"search_queues": {}
}
}search_queues is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Searches for routing queues based on their name, allowing for wildcard searches. Returns a paginated list of matching queues, including their Name, ID, Description (if available), and Member Count (if available). Also provides pagination details like current page, page size, total results found, and total pages available. Useful for finding specific queue IDs, checking queue configurations, or listing available queues. It is categorised as a Read tool in the Genesys Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Genesys Cloud MCP Server MCP server in PolicyLayer and add a rule for search_queues: 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 Genesys Cloud MCP Server. Nothing to install.
search_queues 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 search_queues 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 search_queues. 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.
search_queues is provided by the Genesys Cloud MCP Server MCP server (makingchatbots/genesys-cloud-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Genesys Cloud MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Genesys Cloud MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.