指定されたデバイスの現在のGPS位置情報を取得します。GPSに対応していないデバイスでは利用できません
AI agents call get_device_location to retrieve information from Safie API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves location data from a device without modifying or deleting it, classifying it as Read. Severity is medium because location data exposure could enable physical stalking or targeting, presenting a moderate blast radius if misused by an AI agent, though it is not Financial (no money moved) or Destructive (data not deleted).
From the tool's definition Tool retrieves GPS location information (get_device_location, 現在のGPS位置情報を取得), with no modification of data or triggering of external operations described.
Documented attack patterns abuse exactly the kind of access get_device_location gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Safie API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_device_location:
{
"version": "1",
"default": "deny",
"tools": {
"get_device_location": {}
}
}get_device_location is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
指定されたデバイスの現在のGPS位置情報を取得します。GPSに対応していないデバイスでは利用できません. It is categorised as a Read tool in the Safie API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Safie API MCP Server MCP server in PolicyLayer and add a rule for get_device_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 Safie API MCP Server. Nothing to install.
get_device_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 get_device_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 get_device_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.
get_device_location is provided by the Safie API MCP Server MCP server (safiepublic/safie-api-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Safie API MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Safie API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.