List community-submitted geo layers. These are user-contributed datasets
AI agents call list_submissions 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 tool retrieves and displays existing community-submitted geospatial datasets. It performs a read-only query operation without modifying, executing code, deleting data, or committing financial transactions. The blast radius of misuse is minimal—an AI agent could at most retrieve information about available datasets, which poses no security threat.
From the tool's definition Tool name 'list_submissions' and description 'List community-submitted geo layers. These are user-contributed datasets' indicate a retrieval/query operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_submissions 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 list_submissions:
{
"version": "1",
"default": "deny",
"tools": {
"list_submissions": {}
}
}list_submissions 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.
List community-submitted geo layers. These are user-contributed datasets. 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 list_submissions: 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.
list_submissions 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 list_submissions 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 list_submissions. 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.
list_submissions 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.