Check real-time availability and latency of LLM provider APIs. Monitors Anthropic, OpenAI, Google, Mistral, DeepSeek, and Meta endpoints. Tells you if a service is up before you call it. Costs $0.005 USDC via x402 on Solana. Args: provider: Filter by provider name, or 'all' for everything. ...
Bulk/mass operation — affects multiple targets
Part of the Agent Infrastructure MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call check_availability to retrieve information from Agent Infrastructure without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though check_availability only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
check_availability:
rules:
- action: allowSee the full Agent Infrastructure policy for all 6 tools.
Agents calling read-class tools like check_availability have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Check real-time availability and latency of LLM provider APIs. Monitors Anthropic, OpenAI, Google, Mistral, DeepSeek, and Meta endpoints. Tells you if a service is up before you call it. Costs $0.005 USDC via x402 on Solana. Args: provider: Filter by provider name, or 'all' for everything. Options: anthropic, openai, google, mistral, deepseek, meta, all. It is categorised as a Read tool in the Agent Infrastructure MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for check_availability. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Agent Infrastructure MCP server.
check_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_availability rule in your Intercept 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 Intercept policy for check_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_availability is provided by the Agent Infrastructure MCP server (getkin/agent-infrastructure). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.