check_spot_availability
AI agents call check_spot_availability to retrieve information from Verda Cloud MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool checks spot instance availability—a read-only query operation with no side effects. It retrieves data to inform decisions but does not create, modify, delete, execute, or commit financial actions. Even if an AI agent misused this, it would only retrieve information. The lack of an explicit description slightly lowers confidence from 0.95 to 0.9, but the name and server context are clear.
From the tool's definition Tool name 'check_spot_availability' indicates a query/check operation. The server description confirms it 'supports automated workflows for checking availability'.
Attacks that exploit this kind of access
check_spot_availability. It is categorised as a Read tool in the Verda Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Verda Cloud MCP Server MCP server in PolicyLayer and add a rule for check_spot_availability: 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 Verda Cloud MCP Server. Nothing to install.
check_spot_availability 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 check_spot_availability 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 check_spot_availability. 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.
check_spot_availability is provided by the Verda Cloud MCP Server MCP server (sniper35/verda-cloud-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 →