Get results from an asynchronous query using its query ID.
AI agents call get_query_results to retrieve information from Imply Druid without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves query results using an existing query ID—a pure read operation with no side effects. The read-only nature of the Imply Druid MCP server and the retrieval-only semantics confirm this is a Read category tool with low severity, as it cannot modify data or execute new operations beyond fetching already-computed results.
From the tool's definition Tool description states 'Get results from an asynchronous query using its query ID.' The action is retrieval of pre-computed results without modification.
Attacks that exploit this kind of access
Get results from an asynchronous query using its query ID. It is categorised as a Read tool in the Imply Druid MCP Server, which means it retrieves data without modifying state.
Register the Imply Druid MCP server in PolicyLayer and add a rule for get_query_results: 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 Imply Druid. Nothing to install.
get_query_results 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 get_query_results 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 get_query_results. 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.
get_query_results is provided by the Imply Druid MCP server (yeongbin-hwang/imply-druid-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 →