find_nearest_toilets
Find the nearest public toilets to a location (Australia).
This record as markdown: /tools/creativelead-unclick/find-nearest-toilets.md
What find_nearest_toilets does on UnClick
AI agents call find_nearest_toilets to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | |
radius | number | — | Search radius in metres |
latitude | number | — | |
longitude | number | — |
Parameters from the server's own tool schema.
Why find_nearest_toilets is rated Low
This tool queries a database or service to retrieve information about nearby public toilet locations based on user input. It has no side effects, does not create or modify data, does not execute arbitrary code, does not delete anything, and does not involve financial transactions. It is a straightforward Read operation similar to a search or lookup function.
From the tool's definition Tool name 'find_nearest_toilets' and description 'Find the nearest public toilets to a location (Australia)' indicate a lookup/search operation that retrieves location data without modifying, executing code, deleting data, or moving money.
Attacks that exploit this kind of access
The rule that runs find_nearest_toilets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_nearest_toilets, this is the rule to start with:
find_nearest_toilets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every find_nearest_toilets call is checked against it from then on.
Questions about find_nearest_toilets
Find the nearest public toilets to a location (Australia). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
find_nearest_toilets accepts 4 parameters: limit, radius, latitude, longitude. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for find_nearest_toilets: 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 UnClick. Nothing to install.
find_nearest_toilets 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 find_nearest_toilets 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 find_nearest_toilets. 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.
find_nearest_toilets is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue