Validate EPF establishment code. # PermissionTier: READ_ONLY
AI agents call validate_epf_code 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 data without creating, modifying, deleting, or executing code. The explicit READ_ONLY permission tier confirms it is a retrieval operation. Validation endpoints that check existence or format of identifiers are classified as Read operations.
From the tool's definition Tool name 'validate_epf_code' performs validation/lookup of EPF establishment codes. Description explicitly marks it as 'READ_ONLY' and PermissionTier is READ_ONLY. No side effects, modification, deletion, code execution, or financial transactions occur.
Documented attack patterns abuse exactly the kind of access validate_epf_code 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_epf_code:
{
"version": "1",
"default": "deny",
"tools": {
"validate_epf_code": {}
}
}validate_epf_code 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 EPF establishment code. # 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 validate_epf_code: 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_epf_code 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_epf_code 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_epf_code. 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_epf_code 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.