numbeo_indices_city
Get a Numbeo city's data for an index family. Returns one city's data for a Numbeo index family (quality of life, crime, health care, pollution, traffic, or property investment): headline indices, and (depending on the family) titled sub-index sections and/or itemized prices. Credential-free publ...
This record as markdown: /tools/crawlora-mcp/numbeo-indices-city.md
What numbeo_indices_city does on Crawlora
AI agents call numbeo_indices_city to retrieve information from Crawlora 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 |
|---|---|---|---|
slug | string | Yes | Numbeo city slug |
index | string | Yes | Index family |
Parameters from the server's own tool schema.
Why numbeo_indices_city is rated Low
This tool queries and retrieves publicly available city index data from Numbeo without side effects. It performs a simple data lookup operation with no capability to modify, delete, or execute arbitrary code. The blast radius of misuse is minimal—an agent could only retrieve index data, which is already public.
From the tool's definition Tool description states it 'Returns one city's data' and 'Get a Numbeo city's data' from public sources (numbeo.com). Verbs are retrieval-oriented: 'Get', 'Returns'. No modification, deletion, execution, or financial operations are described.
Attacks that exploit this kind of access
The rule that runs numbeo_indices_city safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For numbeo_indices_city, this is the rule to start with:
numbeo_indices_city 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 Crawlora, apply this rule, and every numbeo_indices_city call is checked against it from then on.
Questions about numbeo_indices_city
Get a Numbeo city's data for an index family. Returns one city's data for a Numbeo index family (quality of life, crime, health care, pollution, traffic, or property investment): headline indices, and (depending on the family) titled sub-index sections and/or itemized prices. Credential-free public Numbeo data (numbeo.com). It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
numbeo_indices_city accepts 2 parameters: slug, index. Required: slug, index. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for numbeo_indices_city: 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 Crawlora. Nothing to install.
numbeo_indices_city 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 numbeo_indices_city 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 numbeo_indices_city. 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.
numbeo_indices_city is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue