search_nearby

Search for places near a location in Apple Maps. If no coordinates are given, searches near the current location.

SERVERIconnect SOURCEiconnect-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/search-nearby.md

What search_nearby does on Iconnect

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

Why search_nearby is rated Low

search_nearby retrieves location-based information with no side effects. It reads public map data and returns results. The optional use of 'current location' as a default parameter does not elevate this beyond a Read operation, as it merely queries data based on implicit context rather than modifying or executing state-changing operations.

From the tool's definition Tool description states it 'Search[es] for places near a location' with no mention of modifications, deletions, or state changes. This is a straightforward query operation against Apple Maps data.

Questions about search_nearby

What does the search_nearby tool do? +

Search for places near a location in Apple Maps. If no coordinates are given, searches near the current location. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_nearby? +

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

What risk level is search_nearby? +

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

Can I rate-limit search_nearby? +

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

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

search_nearby is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Iconnect, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Iconnect's. Pull the full record:

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.