share_location

Generate a shareable Apple Maps link for a 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/share-location.md

WHAT IT DOES

What share_location does on Iconnect

AI agents call share_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.

RISK

Why share_location is rated Low

The tool generates a URL/link for a location — it reads/constructs a shareable link without modifying data, executing commands, or transmitting location to third parties. It is effectively a read/query operation that produces a Maps URL. Minor privacy consideration since it involves location data, but no destructive or financial action occurs.

From the tool's definition Generate a shareable Apple Maps link for a location

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs share_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 share_location, this is the rule to start with:

share_location Allowed

share_location is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "share_location": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every share_location call is checked against it from then on.

FAQ

Questions about share_location

What does the share_location tool do? +

Generate a shareable Apple Maps link for a 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 share_location? +

Register the Iconnect MCP server in PolicyLayer and add a rule for share_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.

What risk level is share_location? +

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

Can I rate-limit share_location? +

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

How do I block share_location completely? +

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

What MCP server provides share_location? +

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

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →