This record as markdown: /tools/heznpc-airmcp/open-address.md
What open_address does on AirMCP
AI agents invoke open_address to trigger actions in AirMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why open_address is rated High
This tool triggers an external application action (launching/navigating Apple Maps to a specific address). It doesn't just read data — it causes a side effect by opening and interacting with the Maps application. No data is created or destroyed, but it executes an external operation.
From the tool's definition Open a specific address in Apple Maps
Attacks that exploit this kind of access
The rule that runs open_address safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For open_address, this is the rule to start with:
open_address stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every open_address call is checked against it from then on.
Questions about open_address
Open a specific address in Apple Maps. It is categorised as a Execute tool in the AirMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Air MCP server in PolicyLayer and add a rule for open_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 AirMCP. Nothing to install.
open_address is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the open_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.
Set action: deny in the PolicyLayer policy for open_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.
open_address is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue