AI agents call get_toilet_details to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
toilet_id | string | Yes |
Parameters from the server's own tool schema.
This tool retrieves information about a public toilet given an ID. It performs a read-only query with no side effects, no data modification, no code execution, and no destructive or financial implications. The data retrieved (public toilet location/facility details) is non-sensitive and informational in nature.
From the tool's definition Tool name 'get_toilet_details' and description 'Get details for a specific public toilet by ID' indicate a retrieval operation with the verb 'Get'.
Attacks that exploit this kind of access
Get details for a specific public toilet by ID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
get_toilet_details accepts 1 parameter: toilet_id. Required: toilet_id. 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 get_toilet_details: 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.
get_toilet_details 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_toilet_details 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_toilet_details. 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_toilet_details is provided by the UnClick MCP server (@unclick/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 →