Analyze Electric Vehicle (EV) registrations across states and categories.
AI agents call get_ev_stats to retrieve information from VAHAN Data MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes EV registration statistics from the VAHAN database. It queries existing data to provide insights without creating, modifying, deleting, or executing any operations. The action is purely informational (read) with no side effects or irreversible consequences.
From the tool's definition Tool name 'get_ev_stats' and description 'Analyze Electric Vehicle (EV) registrations across states and categories' indicate data retrieval and analysis only. No modification, deletion, execution, or financial operations are described.
Attacks that exploit this kind of access
Analyze Electric Vehicle (EV) registrations across states and categories. It is categorised as a Read tool in the VAHAN Data MCP Server MCP Server, which means it retrieves data without modifying state.
Register the VAHAN Data MCP Server MCP server in PolicyLayer and add a rule for get_ev_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 VAHAN Data MCP Server. Nothing to install.
get_ev_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 get_ev_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 get_ev_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.
get_ev_stats is provided by the VAHAN Data MCP Server MCP server (shubhamgrg04/vahanmcp). 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 →