# lookup_ifsc

Retrieves details about an Indian bank branch using its IFSC code (e.g. Bank Name, Branch, Address, Contact, and features like UPI, RTGS, NEFT, IMPS support). Uses caching to optimize response times.

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

## Facts

- Tool: `lookup_ifsc`
- 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 |
| --- | --- | --- | --- |
| `ifsc` | string | yes | The 11-character Indian Financial System Code (e.g., 'HDFC0000123') |

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_ifsc",
    "arguments": {
      "ifsc": "<ifsc>"
    }
  }
}
```

## Why lookup_ifsc is rated Low

This tool performs a straightforward data retrieval operation against Indian banking infrastructure. It queries static reference data (bank branch information) and returns read-only details. There is no capability to modify data, execute code, delete records, or commit financial transactions. The mention of caching is an implementation detail that does not change the fundamental read-only nature.

From the tool's own definition: "Tool name 'lookup_ifsc' and description 'Retrieves details about an Indian bank branch using its IFSC code' indicates a read-only query operation."

## Use case

AI agents call lookup_ifsc 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_ifsc": {}
  }
}
```

## 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_pincode` — Read — https://policylayer.com/tools/denispaul-india-business-mcp-server/lookup-pincode.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