get_user_location

Return {latitude, longitude, gps_accuracy, source, state} for a person.* entity.

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent
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/fistacho-ha-nexus-agent/get-user-location.md

What get_user_location does on Ha Nexus Agent

AI agents call get_user_location to retrieve information from Ha Nexus Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_user_location is rated Low

This tool retrieves geolocation data (latitude, longitude, GPS accuracy, and state) from a Home Assistant person entity. It performs a read-only query with no side effects. While the data retrieved (precise GPS coordinates) is sensitive and could enable privacy violations or physical tracking if misused by an agent, the tool itself does not create, modify, delete, or execute anything.

From the tool's definition Tool description states it 'Return[s] {latitude, longitude, gps_accuracy, source, state}' for a person entity—a pure data retrieval operation with no modification, deletion, or execution of commands.

Questions about get_user_location

What does the get_user_location tool do? +

Return {latitude, longitude, gps_accuracy, source, state} for a person.* entity. It is categorised as a Read tool in the Ha Nexus Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_user_location? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for get_user_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 Ha Nexus Agent. Nothing to install.

What risk level is get_user_location? +

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

Can I rate-limit get_user_location? +

Yes. Add a rate_limit block to the get_user_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 get_user_location completely? +

Set action: deny in the PolicyLayer policy for get_user_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 get_user_location? +

get_user_location is provided by the Ha Nexus Agent MCP server (fistacho/ha-nexus-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Ha Nexus Agent, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ha Nexus Agent's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.