Get, set, or reset the device geolocation (GPS coordinates). Works on both iOS (simulators and real devices) and Android (emulators and real devices with mock location enabled). Use action=get to read current coordinates, action=set with latitude/longitude (and optional altitude for Android) to s...
Part of the MCP Appium - Mobile Development and Automation Server server.
Free to start. No card required.
AI agents may call appium_geolocation to permanently remove or destroy resources in MCP Appium - Mobile Development and Automation Server. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call appium_geolocation in a loop, permanently destroying resources in MCP Appium - Mobile Development and Automation Server. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"appium_geolocation"
]
} See the full MCP Appium - Mobile Development and Automation Server policy for all 54 tools.
These attack patterns abuse exactly the kind of access appium_geolocation gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Get, set, or reset the device geolocation (GPS coordinates). Works on both iOS (simulators and real devices) and Android (emulators and real devices with mock location enabled). Use action=get to read current coordinates, action=set with latitude/longitude (and optional altitude for Android) to simulate a location, or action=reset to restore the system default. Note: On Android emulators, reset is not supported — use action=set to manually restore coordinates instead. On Android real devices, the mocked location may persist until the GPS cache refreshes.. It is categorised as a Destructive tool in the MCP Appium - Mobile Development and Automation Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Appium - Mobile Development and Automation Server MCP server in PolicyLayer and add a rule for appium_geolocation: 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 MCP Appium - Mobile Development and Automation Server. Nothing to install.
appium_geolocation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the appium_geolocation 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 appium_geolocation. 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.
appium_geolocation is provided by the MCP Appium - Mobile Development and Automation Server MCP server (appium-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 54 MCP Appium - Mobile Development and Automation Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.