AI agents call get_waste_calendar to retrieve information from Mcp Swiss without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves publicly available waste collection schedule data for Zurich. It has no side effects, does not modify or delete data, does not execute external operations, and does not involve financial transactions. The operation is purely informational and read-only, consistent with other sibling tools like 'get_air_quality', 'get_arrivals', and 'get_dam_details' that fetch static reference data.
From the tool's definition Tool name 'get_waste_calendar' and description 'Get a full monthly waste collection calendar' indicate data retrieval with no modification, deletion, or execution. Returns calendar information for a given ZIP code.
Attacks that exploit this kind of access
Get a full monthly waste collection calendar for a Zurich city ZIP code. It is categorised as a Read tool in the Mcp Swiss MCP Server, which means it retrieves data without modifying state.
Register the Mcp Swiss MCP server in PolicyLayer and add a rule for get_waste_calendar: 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 Mcp Swiss. Nothing to install.
get_waste_calendar 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_waste_calendar 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_waste_calendar. 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_waste_calendar is provided by the Mcp Swiss MCP server (mcp-swiss). 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 →