Find features from a layer that are near a given point. Samples a grid of points around the
AI agents call nearby to retrieve information from Bharatlas without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a geospatial read/query operation that retrieves features matching spatial criteria. It has no side effects, does not modify data, and does not execute external operations. The blast radius of misuse is minimal—worst case an attacker retrieves inappropriate geographic information about infrastructure or locations, but this is a standard read operation.
From the tool's definition Tool name 'nearby' and description 'Find features from a layer that are near a given point' indicates a spatial query operation that retrieves data based on geographic proximity.
Documented attack patterns abuse exactly the kind of access nearby gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bharatlas, and nothing reaches the server without passing your rules. This is the rule we recommend for nearby:
{
"version": "1",
"default": "deny",
"tools": {
"nearby": {}
}
}nearby 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.
Find features from a layer that are near a given point. Samples a grid of points around the. It is categorised as a Read tool in the Bharatlas MCP Server, which means it retrieves data without modifying state.
Register the Bharatlas MCP server in PolicyLayer and add a rule for nearby: 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 Bharatlas. Nothing to install.
nearby 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 nearby 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 nearby. 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.
nearby is provided by the Bharatlas MCP server (urbanmorph/geodata). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Bharatlas tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 Bharatlas tools catalogued and risk-classified — across an index of 42,500+ MCP servers.