fleet_list_async_queries
AI agents call fleet_list_async_queries to retrieve information from Fleet without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name strongly suggests querying or retrieving a list of asynchronous queries without modifying them. While the description is empty, the naming convention and context from sibling tools indicate this is a retrieval operation with no side effects. Confidence is moderate due to lack of explicit description, but the semantic meaning of 'list' is well-established in API design.
From the tool's definition Tool name 'fleet_list_async_queries' indicates listing/retrieving queries; sibling tools like 'fleet_create_query' and 'fleet_cancel_query' suggest this is a Fleet management system where list operations are read-only.
Documented attack patterns abuse exactly the kind of access fleet_list_async_queries gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fleet, and nothing reaches the server without passing your rules. This is the rule we recommend for fleet_list_async_queries:
{
"version": "1",
"default": "deny",
"tools": {
"fleet_list_async_queries": {}
}
}fleet_list_async_queries 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.
fleet_list_async_queries. It is categorised as a Read tool in the Fleet MCP Server, which means it retrieves data without modifying state.
Register the Fleet MCP server in PolicyLayer and add a rule for fleet_list_async_queries: 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 Fleet. Nothing to install.
fleet_list_async_queries 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 fleet_list_async_queries 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 fleet_list_async_queries. 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.
fleet_list_async_queries is provided by the Fleet MCP server (fleet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Fleet, 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.
85 Fleet tools catalogued and risk-classified — across an index of 43,000+ MCP servers.