Get locations the user visited in the last 30 days. Use this when the user asks about where they were this month or in the last few weeks.
AI agents call get-locations-month 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 personal location history data without creating, modifying, or deleting information. It is a Read operation. Severity is medium because location data is sensitive personal information that could be misused if an AI agent shares it inappropriately or with unauthorized parties, but the tool itself performs no destructive or financial operations.
From the tool's definition Tool name 'get-locations' and description 'Get locations the user visited' indicate data retrieval with no modification. The action is a query operation retrieving historical location data.
Documented attack patterns abuse exactly the kind of access get-locations-month 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-month:
{
"version": "1",
"default": "deny",
"tools": {
"get-locations-month": {}
}
}get-locations-month 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 30 days. Use this when the user asks about where they were this month or in the last few weeks. 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-month: 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-month 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-month 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-month. 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-month 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.