Get import graph neighbors of a file — files it imports and files that import it.
AI agents call get_neighbors to retrieve information from Carto MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a static analysis query of the codebase's import graph to understand file relationships. It has no side effects, creates no changes, executes no code, and poses minimal risk if misused by an AI agent — worst case, it returns graph data that reflects the actual project structure. Categorized as Read per the rule: retrieves or queries data with no side effects.
From the tool's definition Tool description states 'Get import graph neighbors' — a query operation that retrieves information about file dependencies without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access get_neighbors gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Carto MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_neighbors:
{
"version": "1",
"default": "deny",
"tools": {
"get_neighbors": {}
}
}get_neighbors 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 import graph neighbors of a file — files it imports and files that import it. It is categorised as a Read tool in the Carto MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Carto MCP Server MCP server in PolicyLayer and add a rule for get_neighbors: 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 Carto MCP Server. Nothing to install.
get_neighbors 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_neighbors 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_neighbors. 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_neighbors is provided by the Carto MCP Server MCP server (theanshsonkar/carto). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 22 Carto MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
22 Carto MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.