search_by_location_point_distance

search_by_location_point_distance

Server MLIT Data Platform MCP Server mlit-data-platform/mlit-dpf-mcp
Category Read
Risk class Low
Parameters 00 required

What search_by_location_point_distance does on MLIT Data Platform MCP Server

AI agents call search_by_location_point_distance to retrieve information from MLIT Data Platform 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_location_point_distance needs a policy

This is a Read operation that retrieves data based on geographic location parameters. Despite the empty description, the naming convention ('search_by_location_point_distance'), the server's stated purpose of enabling search and retrieval, and the pattern of all sibling tools being GET/search operations indicate this tool queries existing data without modification, deletion, or execution.

From the tool's definition Tool name indicates geographic distance-based search ('search_by_location_point_distance'). All sibling tools are read-only queries (get_all_data, get_data, get_count_data, get_data_catalog, get_municipality_data, get_prefecture_data, get_mesh).

Questions about search_by_location_point_distance

What does the search_by_location_point_distance tool do? +

search_by_location_point_distance. It is categorised as a Read tool in the MLIT Data Platform MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_by_location_point_distance? +

Register the MLIT Data Platform MCP Server MCP server in PolicyLayer and add a rule for search_by_location_point_distance: 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 MLIT Data Platform MCP Server. Nothing to install.

What risk level is search_by_location_point_distance? +

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

Can I rate-limit search_by_location_point_distance? +

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

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

search_by_location_point_distance is provided by the MLIT Data Platform MCP Server MCP server (mlit-data-platform/mlit-dpf-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.