AI agents call validate_driving_license to retrieve information from Mcp India Stack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Validation and lookup tools retrieve or query data to check validity against a database without creating, modifying, or deleting records. The sibling validation tools (Aadhaar, GSTIN, PAN, IFSC) are all Read operations. Driving license validation would follow the same pattern—checking a number against a registry to confirm it exists and is valid. No side effects or irreversible actions are implied.
From the tool's definition Tool name 'validate_driving_license' indicates a validation/lookup operation, consistent with sibling tools like 'bulk_validate_aadhaar', 'bulk_validate_gstin', 'bulk_validate_pan', and 'bulk_validate_ifsc' which all perform identity or document validation…
Documented attack patterns abuse exactly the kind of access validate_driving_license gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp India Stack, and nothing reaches the server without passing your rules. This is the rule we recommend for validate_driving_license:
{
"version": "1",
"default": "deny",
"tools": {
"validate_driving_license": {}
}
}validate_driving_license is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
validate_driving_license. It is categorised as a Read tool in the Mcp India Stack MCP Server, which means it retrieves data without modifying state.
Register the Mcp India Stack MCP server in PolicyLayer and add a rule for validate_driving_license: 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 India Stack. Nothing to install.
validate_driving_license 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 validate_driving_license 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 validate_driving_license. 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.
validate_driving_license is provided by the Mcp India Stack MCP server (rehan1020/mcp-india-stack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp India Stack, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
58 Mcp India Stack tools catalogued and risk-classified — across an index of 43,000+ MCP servers.