Check if the EPA Air Quality System (AQS) API is operational.
AI agents call aqs_is_available to retrieve information from EPA Air Quality System (AQS) MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query to determine API availability status. It retrieves information (operational state) with no side effects, no data modification, and no execution of commands or deletion of data. It is a simple health-check read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'aqs_is_available' and description 'Check if the EPA Air Quality System (AQS) API is operational' indicate a status/health check operation that retrieves operational state without modifying any data.
Attacks that exploit this kind of access
Check if the EPA Air Quality System (AQS) API is operational. It is categorised as a Read tool in the EPA Air Quality System (AQS) MCP Server MCP Server, which means it retrieves data without modifying state.
Register the EPA Air Quality System (AQS) MCP Server MCP server in PolicyLayer and add a rule for aqs_is_available: 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 EPA Air Quality System (AQS) MCP Server. Nothing to install.
aqs_is_available 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 aqs_is_available 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 aqs_is_available. 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.
aqs_is_available is provided by the EPA Air Quality System (AQS) MCP Server MCP server (tyson-swetnam/aqs-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 →