AI agents call bulk_validate_aadhaar 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.
This tool retrieves and validates identity data (Aadhaar numbers) without modifying it, placing it in the Read category. Severity is medium because while validation itself is non-destructive, Aadhaar is sensitive PII in the Indian context, and bulk validation of personal identity data carries risks if misused for enumeration, privacy breaches, or unauthorized identity checks.
From the tool's definition Tool name 'bulk_validate_aadhaar' indicates batch validation of Aadhaar numbers. The sibling tool 'build_aa_consent_request' and description context ('identity validation (PAN, Aadhaar, GSTIN)') confirm this performs validation/verification queries.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access bulk_validate_aadhaar 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 bulk_validate_aadhaar:
{
"version": "1",
"default": "deny",
"tools": {
"bulk_validate_aadhaar": {}
}
}bulk_validate_aadhaar 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.
bulk_validate_aadhaar. 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 bulk_validate_aadhaar: 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.
bulk_validate_aadhaar 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 bulk_validate_aadhaar 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 bulk_validate_aadhaar. 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.
bulk_validate_aadhaar 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.