query_async_job_result

What query_async_job_result does on CloudStack MCP Server

AI agents call query_async_job_result to retrieve information from CloudStack MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why query_async_job_result is rated Low

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.

The rule that runs query_async_job_result safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CloudStack MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For query_async_job_result, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_async_job_result": {}
  }
}

Questions about query_async_job_result