get_customer_geographic_access_scope
Manage country-based access to tenants in your customer hierarchy. Returns the geographic scope for a target customer. The authenticated tenant must be the hierarchy root, and the target must be that root customer or one of its child customers. Targets outside that hierarchy are returned as not f...
This record as markdown: /tools/doit/get-customer-geographic-access-scope.md
What get_customer_geographic_access_scope does on Doit
AI agents call get_customer_geographic_access_scope to retrieve information from Doit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
X-Tenant-Id | string | — | |
customerContext | string | — | Scope the request to a specific customer by ID. Required for DoiT employees (whose token isn't tied to a single customer); omit for direct customer users. |
targetCustomerId | string | Yes |
Parameters from the server's own tool schema.
Why get_customer_geographic_access_scope is rated Low
Even though get_customer_geographic_access_scope only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs get_customer_geographic_access_scope safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Doit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_customer_geographic_access_scope, this is the rule to start with:
get_customer_geographic_access_scope is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Doit, apply this rule, and every get_customer_geographic_access_scope call is checked against it from then on.
Questions about get_customer_geographic_access_scope
Manage country-based access to tenants in your customer hierarchy. Returns the geographic scope for a target customer. The authenticated tenant must be the hierarchy root, and the target must be that root customer or one of its child customers. Targets outside that hierarchy are returned as not found. Requires the UsersManager permission. It is categorised as a Read tool in the Doit MCP Server, which means it retrieves data without modifying state.
get_customer_geographic_access_scope accepts 3 parameters: X-Tenant-Id, customerContext, targetCustomerId. Required: targetCustomerId. The full parameter table on this page comes from the server's own tool schema.
Register the Doit MCP server in PolicyLayer and add a rule for get_customer_geographic_access_scope: 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 Doit. Nothing to install.
get_customer_geographic_access_scope 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_customer_geographic_access_scope 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_customer_geographic_access_scope. 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_customer_geographic_access_scope is provided by the Doit MCP server (@doitintl/doit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Doit, and thousands of servers like it.
This server
Across the catalogue