GeoIP 由来の大まかな場所文字列を返す基本機能
AI agents call where-are-we to retrieve information from Local Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves geolocation information derived from GeoIP data, which is a read-only operation that queries and returns information without side effects. No data is created, modified, deleted, or executed. The 'approximate' qualifier further suggests it returns cached or estimated data rather than performing real-time operations.
From the tool's definition Tool description states it 'returns basic functionality' of 'approximate location string from GeoIP' - a data retrieval operation with no modification, deletion, or code execution.
Attacks that exploit this kind of access
GeoIP 由来の大まかな場所文字列を返す基本機能. It is categorised as a Read tool in the Local Context MCP Server, which means it retrieves data without modifying state.
Register the Local Context MCP server in PolicyLayer and add a rule for where-are-we: 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 Local Context. Nothing to install.
where-are-we 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 where-are-we 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 where-are-we. 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.
where-are-we is provided by the Local Context MCP server (obaratch/local-context-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
where-are-we is one line of Local Context's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →