lookup_zipcode

Look up the Japanese address for a 7-digit postal code (郵便番号). Returns prefecture, city, and town(s) in kanji, katakana, and romaji, plus the JIS prefecture code and Soumu city code. Hyphens in the input are allowed.

Server jpzip MCP server jpzip/mcp
Category Read
Risk class Low
Parameters 00 required

What lookup_zipcode does on jpzip MCP server

AI agents call lookup_zipcode to retrieve information from jpzip MCP server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why lookup_zipcode needs a policy

This tool retrieves postal code data from a Japanese address dataset and returns formatted address information. It has no side effects, does not create, modify, or delete data, and does not execute arbitrary code or commands. It is a straightforward read-only query operation with minimal security risk.

From the tool's definition Tool description states 'Look up the Japanese address' and 'Returns prefecture, city, and town(s)' — purely a retrieval operation with no modification, deletion, or execution of code.

Questions about lookup_zipcode

What does the lookup_zipcode tool do? +

Look up the Japanese address for a 7-digit postal code (郵便番号). Returns prefecture, city, and town(s) in kanji, katakana, and romaji, plus the JIS prefecture code and Soumu city code. Hyphens in the input are allowed. It is categorised as a Read tool in the jpzip MCP server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lookup_zipcode? +

Register the jpzip MCP server MCP server in PolicyLayer and add a rule for lookup_zipcode: 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 jpzip MCP server. Nothing to install.

What risk level is lookup_zipcode? +

lookup_zipcode is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit lookup_zipcode? +

Yes. Add a rate_limit block to the lookup_zipcode 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.

How do I block lookup_zipcode completely? +

Set action: deny in the PolicyLayer policy for lookup_zipcode. 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.

What MCP server provides lookup_zipcode? +

lookup_zipcode is provided by the jpzip MCP server MCP server (jpzip/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.