openchargemap_search
Find EV charging stations near a location from Open Charge Map.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/openchargemap-search.md
What openchargemap_search does on UnClick
AI agents call openchargemap_search to retrieve information from UnClick 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 |
|---|---|---|---|
distance | number | — | Search radius in km (default 10). |
latitude | number | Yes | Latitude. |
longitude | number | Yes | Longitude. |
max_results | number | — | Max stations (default 10, max 50). |
Parameters from the server's own tool schema.
Why openchargemap_search is rated Low
This tool queries a public database (Open Charge Map) to locate EV charging stations by geographic proximity. It performs a read-only information lookup with no capability to modify, delete, or execute external operations. The blast radius of misuse is minimal — an agent could only retrieve station location data, which is already public.
From the tool's definition Tool name contains 'search' and description states 'Find EV charging stations near a location' — a query operation that retrieves data with no side effects.
Attacks that exploit this kind of access
The rule that runs openchargemap_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openchargemap_search, this is the rule to start with:
openchargemap_search 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 UnClick, apply this rule, and every openchargemap_search call is checked against it from then on.
Questions about openchargemap_search
Find EV charging stations near a location from Open Charge Map. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
openchargemap_search accepts 4 parameters: distance, latitude, longitude, max_results. Required: latitude, longitude. 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 openchargemap_search: 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.
openchargemap_search 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 openchargemap_search 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 openchargemap_search. 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.
openchargemap_search 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue