list_gcp_billing_accounts_settings

SERVERDoit SOURCE@doitintl/doit-mcp-server

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/doit/list-gcp-billing-accounts-settings.md

WHAT IT DOES

What list_gcp_billing_accounts_settings does on Doit

AI agents call list_gcp_billing_accounts_settings 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
`pageToken`	string	—
`maxResults`	number	—
`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.

Parameters from the server's own tool schema.

RISK

Why list_gcp_billing_accounts_settings is rated Low

Even though list_gcp_billing_accounts_settings 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_gcp_billing_accounts_settings 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 list_gcp_billing_accounts_settings, this is the rule to start with:

list_gcp_billing_accounts_settings Allowed

list_gcp_billing_accounts_settings is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_gcp_billing_accounts_settings": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Doit, apply this rule, and every list_gcp_billing_accounts_settings call is checked against it from then on.

FAQ

Questions about list_gcp_billing_accounts_settings

What does the list_gcp_billing_accounts_settings tool do? +

Evaluate current GCP commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns one item per onboarded GCP Billing Account. Each item includes that billing account's recommendation and automation engine settings for each product line activated on it, per region scope: one global entry for compute, and one entry per known region for cloud_sql. Cloud SQL regions come from the billing account's persisted settings: a region is added when eligible spend is first seen there and is never removed, so its settings entry remains listed even if spend later drops to zero. Items are sorted by billingAccountId; within an item, services lists compute before cloud_sql, with cloud_sql regions sorted alphabetically. Settings are stored independently on each billing account. Existing customer-level settings are copied lazily when an account is first read or initialized; if no valid legacy value exists, the complete backend defaults are materialized once on the account. Only product lines that are activated/onboarded for a given billing account are returned. In the DoiT Console, these settings are edited on an account's Settings tab. This endpoint is paginated: a response with a non-empty pageToken has more results, returned when that value is passed as the pageToken parameter. A missing, null, or empty pageToken marks the last page. It is categorised as a Read tool in the Doit MCP Server, which means it retrieves data without modifying state.

What parameters does list_gcp_billing_accounts_settings accept? +

list_gcp_billing_accounts_settings accepts 4 parameters: pageToken, maxResults, X-Tenant-Id, customerContext. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_gcp_billing_accounts_settings? +

Register the Doit MCP server in PolicyLayer and add a rule for list_gcp_billing_accounts_settings: 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.

What risk level is list_gcp_billing_accounts_settings? +

list_gcp_billing_accounts_settings is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_gcp_billing_accounts_settings? +

Yes. Add a rate_limit block to the list_gcp_billing_accounts_settings 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.

How do I block list_gcp_billing_accounts_settings completely? +

Set action: deny in the PolicyLayer policy for list_gcp_billing_accounts_settings. 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.

What MCP server provides list_gcp_billing_accounts_settings? +

list_gcp_billing_accounts_settings 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.

KEEP EXPLORING

More on Doit, and thousands of servers like it.

This server

All 238 Doit tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →