AI agents call get_waste_collection 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 fetches and returns waste collection schedule information for a specified Zurich ZIP code. It performs a simple data retrieval operation without creating, modifying, deleting, or executing any actions. The data returned is factual scheduling information from public municipal records. No financial transactions, destructive operations, or code execution is involved.
From the tool's definition Tool description states 'Get upcoming waste collection dates' and 'Returns the next scheduled pickups' — purely retrieves/queries public data with no side effects.
Attacks that exploit this kind of access
Get upcoming waste collection dates for a Zurich city ZIP code. Returns the next scheduled pickups sorted by date. 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_collection: 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_collection 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_collection 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_collection. 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_collection 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 →