This record as markdown: /tools/io-github-heznpc-iconnect/search-location.md
What search_location does on Iconnect
AI agents call search_location 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_location is rated Low
This tool retrieves location data from Apple Maps in response to a search query. It is a read-only operation that does not create, modify, delete, or execute any side effects. The worst plausible misuse would be mapping a user's search history, a low-severity information disclosure concern.
From the tool's definition Tool name 'search_location' and description 'Search for a place or location in Apple Maps' indicate a query operation with no data modification or external action execution.
Attacks that exploit this kind of access
The rule that runs search_location safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_location, this is the rule to start with:
search_location is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every search_location call is checked against it from then on.
Questions about search_location
Search for a place or location in Apple Maps. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.
Register the Iconnect MCP server in PolicyLayer and add a rule for search_location: 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.
search_location is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_location 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.
Set action: deny in the PolicyLayer policy for search_location. 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.
search_location 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.
This server
Across the catalogue