List all Turkish cities (iller) recognized by YÖKATLAS.
AI agents call list_cities to retrieve information from YOKATLAS API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns static reference data (city names) from the YÖKATLAS database. It performs a simple read operation with no capability to modify, delete, or execute actions. The blast radius of misuse is minimal—an LLM cannot cause harm by retrieving a list of cities. Confidence is high due to explicit 'list' action and clear informational purpose.
From the tool's definition Tool name 'list_cities' and description 'List all Turkish cities' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_cities gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and YOKATLAS API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_cities:
{
"version": "1",
"default": "deny",
"tools": {
"list_cities": {}
}
}list_cities is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all Turkish cities (iller) recognized by YÖKATLAS. It is categorised as a Read tool in the YOKATLAS API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the YOKATLAS API MCP Server MCP server in PolicyLayer and add a rule for list_cities: 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 YOKATLAS API MCP Server. Nothing to install.
list_cities 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 list_cities 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 list_cities. 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.
list_cities is provided by the YOKATLAS API MCP Server MCP server (saidsurucu/yokatlas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 YOKATLAS API MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 YOKATLAS API MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.