ev.charging.details

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ev.charging.details.md

WHAT IT DOES

What ev.charging.details does on Apibase

AI agents call ev.charging.details to retrieve information from Apibase 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
`id`	integer	Yes	Open Charge Map station ID — get from search or nearby results

Parameters from the server's own tool schema.

RISK

Why ev.charging.details is rated Low

Retrieves public EV charging station information with no side effects or data modification.

From the tool's definition Get full details for a specific EV charging station by ID

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ev.charging.details safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ev.charging.details, this is the rule to start with:

ev.charging.details Allowed

ev.charging.details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ev.charging.details": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every ev.charging.details call is checked against it from then on.

FAQ

Questions about ev.charging.details

What does the ev.charging.details tool do? +

Get full details for a specific EV charging station by ID — address, GPS coordinates, all connectors with type/power/status, network operator, usage cost, verification date, number of charging points. Use station ID from search or nearby results (Open Charge Map). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does ev.charging.details accept? +

ev.charging.details accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ev.charging.details? +

Register the Apibase MCP server in PolicyLayer and add a rule for ev.charging.details: 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 Apibase. Nothing to install.

What risk level is ev.charging.details? +

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

Can I rate-limit ev.charging.details? +

Yes. Add a rate_limit block to the ev.charging.details 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 ev.charging.details completely? +

Set action: deny in the PolicyLayer policy for ev.charging.details. 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 ev.charging.details? +

ev.charging.details is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →