AI agents call get_air_quality_stations to retrieve information from Golemio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves air quality station data from a public city data API. It queries existing information without modifying, deleting, or executing external operations. The tool name and server context indicate it is a getter/query function on an open data platform, consistent with other read-only city data retrieval tools. No side effects or data mutation occurs.
From the tool's definition Tool name 'get_air_quality_stations' indicates data retrieval. Server description states it 'enables AI assistants to query Prague's public transit departures, air quality, parking availability, and other city data.' All sibling tools (get_bicycle_counters,…
Attacks that exploit this kind of access
get_air_quality_stations. It is categorised as a Read tool in the Golemio MCP Server, which means it retrieves data without modifying state.
Register the Golemio MCP server in PolicyLayer and add a rule for get_air_quality_stations: 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 Golemio. Nothing to install.
get_air_quality_stations 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 get_air_quality_stations 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 get_air_quality_stations. 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.
get_air_quality_stations is provided by the Golemio MCP server (mrmebelman/golemio-mcp-server). 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 →