Check the status of an asynchronous query.
AI agents call get_query_status 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 queries the status of an existing asynchronous query execution. It retrieves information about a previously submitted query (via execute_async_query) but does not modify data, execute new queries, delete anything, or perform financial transactions. The server is explicitly described as 'read-only,' and status-checking is a passive information retrieval operation with no side effects.
From the tool's definition Tool name 'get_query_status' and description 'Check the status of an asynchronous query' indicate a read-only operation that retrieves query execution status without modifying data or executing operations.
Attacks that exploit this kind of access
Check the status of an asynchronous query. 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_status: 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_status 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_status 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_status. 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_status 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 →