Query the result of an asynchronous job
AI agents call query_async_job_result to retrieve information from CloudStack MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that retrieves job status/results. It has no side effects and does not modify, delete, or execute any infrastructure changes. The blast radius is minimal as it only accesses already-computed results. Confidence is high because the description explicitly uses 'query' (a retrieval verb) and the tool operates on job results, not on actual resources.
From the tool's definition Tool name 'query_async_job_result' and description 'Query the result of an asynchronous job' indicate a retrieval operation that only reads the status and results of previously executed jobs without creating, modifying, or deleting any data.
Attacks that exploit this kind of access
Query the result of an asynchronous job. It is categorised as a Read tool in the CloudStack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for query_async_job_result: 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 CloudStack MCP Server. Nothing to install.
query_async_job_result 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 query_async_job_result 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 query_async_job_result. 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.
query_async_job_result is provided by the CloudStack MCP Server MCP server (mozg31337/cloudstack-mcp-server). 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 →