Get column names, types, and sample values for a layer.
AI agents call get_layer_schema 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 metadata about a layer's structure (schema information) without creating, modifying, deleting, or executing any operations. It is purely informational and has no side effects. Classified as Read with low severity since schema inspection poses minimal risk to confidentiality or integrity of sensitive data.
From the tool's definition Tool description states 'Get column names, types, and sample values for a layer' - a retrieval operation with no modification or execution capability. The server context (Query India's open geo data in natural language) confirms this is a data inspection tool.
Documented attack patterns abuse exactly the kind of access get_layer_schema 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 get_layer_schema:
{
"version": "1",
"default": "deny",
"tools": {
"get_layer_schema": {}
}
}get_layer_schema 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 column names, types, and sample values for a layer. 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 get_layer_schema: 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.
get_layer_schema 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_layer_schema 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_layer_schema. 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_layer_schema 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.