OSM Taginfo: get usage counts (all / nodes / ways / relations) for a specific OpenStreetMap key=value tag, e.g. amenity=cafe. Keyless.
AI agents call tag_stats 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 |
|---|---|---|---|
key | string | Yes | An OSM key, e.g. "amenity". |
value | string | Yes | An OSM value for that key, e.g. "cafe". |
Parameters from the server's own tool schema.
The tool retrieves and returns read-only statistics about OpenStreetMap tag usage. There are no side effects, data modifications, destructive operations, financial transactions, or code execution. The blast radius of misuse is minimal—an agent could only retrieve aggregate statistics about the OSM dataset, which is public information. This is a straightforward Read category tool.
From the tool's definition Tool description states 'get usage counts' for OpenStreetMap tags. This is a retrieval operation that queries statistical metadata about tag usage (nodes, ways, relations counts) with no modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
OSM Taginfo: get usage counts (all / nodes / ways / relations) for a specific OpenStreetMap key=value tag, e.g. amenity=cafe. Keyless. It is categorised as a Read tool in the Mcp Taginfo MCP Server, which means it retrieves data without modifying state.
tag_stats accepts 2 parameters: key, value. Required: key, value. 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 tag_stats: 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.
tag_stats 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 tag_stats 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 tag_stats. 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.
tag_stats 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 →