search_by_address

Search for postal codes by free-text address query. Matches against prefecture, city, and town in kanji, katakana, or romaji (case-insensitive substring match, whitespace ignored). First call in a session downloads the full dataset (~25MB) into memory; subsequent calls within the same session are...

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

What search_by_address does on jpzip MCP server

AI agents call search_by_address 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 search_by_address needs a policy

This tool retrieves information from a Japanese postal code dataset without modifying, deleting, or executing any operations. It is a straightforward read operation with no side effects. The dataset download is a technical implementation detail and does not change the fundamental read-only nature of the tool.

From the tool's definition Tool performs a 'search' operation that 'matches against' existing data and returns postal codes based on address queries. No modification, deletion, or code execution occurs.

Questions about search_by_address

What does the search_by_address tool do? +

Search for postal codes by free-text address query. Matches against prefecture, city, and town in kanji, katakana, or romaji (case-insensitive substring match, whitespace ignored). First call in a session downloads the full dataset (~25MB) into memory; subsequent calls within the same session are instant. 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 search_by_address? +

Register the jpzip MCP server MCP server in PolicyLayer and add a rule for search_by_address: 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 search_by_address? +

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

Can I rate-limit search_by_address? +

Yes. Add a rate_limit block to the search_by_address 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 search_by_address completely? +

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

search_by_address 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.