Get all import edges that cross domain boundaries. Use to detect unexpected coupling.
AI agents call get_cross_domain 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 retrieves and analyzes import graph data from the codebase to identify cross-domain dependencies. It is purely informational—it reads the existing project structure and import relationships without creating, modifying, deleting, or executing anything. This is a classic Read category tool with minimal security risk, appropriate for an AI agent to use for understanding code architecture.
From the tool's definition Tool name 'get_cross_domain' and description 'Get all import edges that cross domain boundaries' indicate a retrieval operation. The verb 'Get' and the intent to 'detect' coupling describe querying behavior with no modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access get_cross_domain 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_cross_domain:
{
"version": "1",
"default": "deny",
"tools": {
"get_cross_domain": {}
}
}get_cross_domain 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 all import edges that cross domain boundaries. Use to detect unexpected coupling. 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_cross_domain: 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_cross_domain 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_cross_domain 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_cross_domain. 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_cross_domain 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.