OSM Taginfo: search OpenStreetMap keys by text, ranked by total usage. Useful for discovering how features are tagged in OSM. Keyless.
AI agents call search_keys to retrieve information from Mcp Taginfo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max keys to return (default 20). |
query | string | Yes | Text to search keys for, e.g. "cuisine". |
Parameters from the server's own tool schema.
This tool queries and retrieves statistical information about OpenStreetMap tags without modifying, executing operations, or deleting data. It is a search/discovery function that returns read-only results. The low severity reflects minimal blast radius—misuse would only return unwanted search results, not cause harm to systems or data.
From the tool's definition The tool description states it 'search[es] OpenStreetMap keys by text, ranked by total usage' and is 'Useful for discovering how features are tagged in OSM.' The verb 'search' combined with 'discovering' and querying metadata about tag usage indicates a…
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
OSM Taginfo: search OpenStreetMap keys by text, ranked by total usage. Useful for discovering how features are tagged in OSM. Keyless. It is categorised as a Read tool in the Mcp Taginfo MCP Server, which means it retrieves data without modifying state.
search_keys accepts 2 parameters: limit, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Taginfo MCP server in PolicyLayer and add a rule for search_keys: 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 Taginfo. Nothing to install.
search_keys 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 search_keys 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 search_keys. 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.
search_keys is provided by the Mcp Taginfo MCP server (pipeworx-io/mcp-taginfo). 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 →