Decode DigiLocker document URI and map to validator. # PermissionTier: READ_ONLY
AI agents call decode_digilocker_uri 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 decodes information from a DigiLocker URI (a document reference system in India) and maps it to a validator. It performs data retrieval and interpretation only, with no side effects, reversible modifications, code execution, or financial operations. The explicit READ_ONLY permission tier confirms this classification as a Read operation with low severity and high confidence.
From the tool's definition Tool name is 'decode_digilocker_uri' and description explicitly states 'PermissionTier: READ_ONLY'. The function decodes and maps a URI to a validator without modifying, deleting, or executing external operations.
Documented attack patterns abuse exactly the kind of access decode_digilocker_uri 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 decode_digilocker_uri:
{
"version": "1",
"default": "deny",
"tools": {
"decode_digilocker_uri": {}
}
} decode_digilocker_uri 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.
Decode DigiLocker document URI and map to validator. # PermissionTier: READ_ONLY. 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 decode_digilocker_uri: 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.
decode_digilocker_uri 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 decode_digilocker_uri 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 decode_digilocker_uri. 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.
decode_digilocker_uri 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.