Get locations the user visited in the last 24 hours. Use this when the user asks about where they were today or in the last day.
AI agents call get-locations-today to retrieve information from BeeMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only retrieval operation that queries location history data. It has no side effects, does not modify or delete data, and does not execute commands or trigger external operations. The blast radius of misuse is minimal — an AI agent could retrieve location history, but cannot alter it or take destructive actions.
From the tool's definition Tool name is 'get-locations-today' and description states 'Get locations the user visited in the last 24 hours' — purely retrieves historical location data with no modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access get-locations-today gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BeeMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get-locations-today:
{
"version": "1",
"default": "deny",
"tools": {
"get-locations-today": {}
}
}get-locations-today 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.
Get locations the user visited in the last 24 hours. Use this when the user asks about where they were today or in the last day. It is categorised as a Read tool in the BeeMCP MCP Server, which means it retrieves data without modifying state.
Register the Bee MCP server in PolicyLayer and add a rule for get-locations-today: 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 BeeMCP. Nothing to install.
get-locations-today 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-locations-today 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-locations-today. 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-locations-today is provided by the Bee MCP server (okgodoit/beemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 BeeMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
19 BeeMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.