get_station

Get full detail for a single EV charging station by its Open Charge Map POI ID. Returns the connector types (CCS/CHAdeMO/Tesla connectors), charging speed (kW), operator, status, plus user comments and last-verified date.

Server Mcp Openchargemap https://gateway.pipeworx.io/openchargemap/mcp
Category Read
Risk class Low
Parameters 21 required

What get_station does on Mcp Openchargemap

AI agents call get_station to retrieve information from Mcp Openchargemap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
id number Yes Open Charge Map POI ID (e.g. from find_stations results).
_apiKey string Optional — your own Open Charge Map API key for higher limits; works without one.

Parameters from the server's own tool schema.

Why get_station needs a policy

This tool performs a pure read operation—querying and retrieving detailed information about an EV charging station by its ID. It returns static/informational data (connector types, charging speed, operator, status, comments, verification date) without creating, modifying, deleting, or executing any operations. No financial transactions or irreversible changes are involved.

From the tool's definition Tool description states it 'Get[s] full detail for a single EV charging station' and 'Returns the connector types, charging speed, operator, status, plus user comments and last-verified date.' The verb 'Get' and the return-only nature indicate data retrieval…

Questions about get_station

What does the get_station tool do? +

Get full detail for a single EV charging station by its Open Charge Map POI ID. Returns the connector types (CCS/CHAdeMO/Tesla connectors), charging speed (kW), operator, status, plus user comments and last-verified date. It is categorised as a Read tool in the Mcp Openchargemap MCP Server, which means it retrieves data without modifying state.

What parameters does get_station accept? +

get_station accepts 2 parameters: id, _apiKey. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_station? +

Register the Mcp Openchargemap MCP server in PolicyLayer and add a rule for get_station: 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 Openchargemap. Nothing to install.

What risk level is get_station? +

get_station is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_station? +

Yes. Add a rate_limit block to the get_station 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.

How do I block get_station completely? +

Set action: deny in the PolicyLayer policy for get_station. 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.

What MCP server provides get_station? +

get_station is provided by the Mcp Openchargemap MCP server (https://gateway.pipeworx.io/openchargemap/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.