Get locations within a specific time range. Use this when the user asks about where they were during a particular period. start_time and end_time should be ISO 8601 formatted date-time strings, in this format: 2025-12-31T00:00:00Z
AI agents call get-locations-by-time 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 tool retrieves or queries personal location history data from the Bee wearable without modifying, deleting, or executing external operations. It is purely informational. The severity is low because the blast radius of misuse is limited to unauthorized disclosure of personal location information, though this is a privacy concern, it does not involve destructive actions, financial impact, or code execution.
From the tool's definition Tool name 'get-locations-by-time' and description 'Get locations within a specific time range' indicate a retrieval operation with no side effects. The parameters (start_time, end_time) are filters for querying historical location data.
Documented attack patterns abuse exactly the kind of access get-locations-by-time 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-by-time:
{
"version": "1",
"default": "deny",
"tools": {
"get-locations-by-time": {}
}
}get-locations-by-time 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 within a specific time range. Use this when the user asks about where they were during a particular period. start_time and end_time should be ISO 8601 formatted date-time strings, in this format: 2025-12-31T00:00:00Z. 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-by-time: 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-by-time 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-by-time 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-by-time. 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-by-time 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.