# lookup_pincode

Retrieves location details for an Indian Postal PIN code (e.g., Post Office name, Block, Circle, District, State). Uses caching to optimize response times.

Agent View of the PolicyLayer registry record for `lookup_pincode`. HTML page: https://policylayer.com/tools/denispaul-india-business-mcp-server/lookup-pincode

## Facts

- Tool: `lookup_pincode`
- Server: India Business (`@denispaul/india-business-mcp-server`) — https://policylayer.com/tools/denispaul-india-business-mcp-server.md
- Install: `npx -y @denispaul/india-business-mcp-server`
- Homepage: https://www.npmjs.com/package/@denispaul/india-business-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `pincode` | string | yes | The 6-digit PIN code (e.g., '560001') |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "lookup_pincode",
    "arguments": {
      "pincode": "<pincode>"
    }
  }
}
```

## Why lookup_pincode is rated Low

This is a straightforward data retrieval tool that queries postal location information for a given PIN code. It has no side effects, cannot modify or delete data, and does not execute code or trigger external operations. The caching mechanism mentioned is purely for performance optimization and does not change the read-only nature of the operation.

From the tool's own definition: "Tool description states it 'Retrieves location details' and 'lookup' is a retrieval operation. The tool fetches read-only postal information (Post Office name, Block, Circle, District, State) with no modification, deletion, or execution capabilities."

## Use case

AI agents call lookup_pincode to retrieve information from India Business without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches India Business:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "lookup_pincode": {}
  }
}
```

## Other tools on India Business (5)

- `calculate_gst_tax` — Read — https://policylayer.com/tools/denispaul-india-business-mcp-server/calculate-gst-tax.md
- `check_pincode_serviceability` — Read — https://policylayer.com/tools/denispaul-india-business-mcp-server/check-pincode-serviceability.md
- `lookup_ifsc` — Read — https://policylayer.com/tools/denispaul-india-business-mcp-server/lookup-ifsc.md
- `validate_gstin` — Read — https://policylayer.com/tools/denispaul-india-business-mcp-server/validate-gstin.md
- `validate_pan` — Read — https://policylayer.com/tools/denispaul-india-business-mcp-server/validate-pan.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=denispaul-india-business-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/denispaul-india-business-mcp-server