This record as markdown: /tools/heznpc-airmcp/drop-pin.md
What drop_pin does on AirMCP
AI agents invoke drop_pin 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 drop_pin is rated High
This tool triggers an external operation in Apple Maps (dropping a pin at coordinates). It's not purely reading data, nor writing persistent data, nor destructive. It executes a UI/application action whose effect is placing a map marker, which is a transient operation in the Maps app.
From the tool's definition Drop a pin at specific coordinates in Apple Maps
Attacks that exploit this kind of access
The rule that runs drop_pin 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 drop_pin, this is the rule to start with:
drop_pin 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 drop_pin call is checked against it from then on.
Questions about drop_pin
Drop a pin at specific coordinates 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 drop_pin: 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.
drop_pin 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 drop_pin 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 drop_pin. 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.
drop_pin 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