AI agents call list_async_jobs 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 straightforward query/list operation that retrieves information about async jobs. It has no side effects, does not execute commands, does not modify infrastructure, and does not delete or move resources. The blast radius of misuse is minimal—an AI agent with access could only view job histories and statuses, which is read-only data retrieval.
From the tool's definition Tool name 'list_async_jobs' and description 'List asynchronous jobs' indicate a retrieval operation that queries the status or history of async operations without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access list_async_jobs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CloudStack MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_async_jobs:
{
"version": "1",
"default": "deny",
"tools": {
"list_async_jobs": {}
}
}list_async_jobs 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.
List asynchronous jobs. 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 list_async_jobs: 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.
list_async_jobs 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 list_async_jobs 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 list_async_jobs. 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.
list_async_jobs is provided by the CloudStack MCP Server MCP server (phantosmax/cloudstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CloudStack MCP Server, 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.
45 CloudStack MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.