list_commitment_policies
Cloud-agnostic PerfectScale for Commitments resources — commitment policies shared by AWS and GCP. Returns every commitment policy available to the tenant: the three built-in policies (conservative, balanced, max_savings) followed by the tenant's own custom policies. Commitment policies are cloud...
This record as markdown: /tools/doit/list-commitment-policies.md
What list_commitment_policies does on Doit
AI agents call list_commitment_policies 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.
Why list_commitment_policies is rated Low
Even though list_commitment_policies 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
The rule that runs list_commitment_policies 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_commitment_policies, this is the rule to start with:
list_commitment_policies 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 list_commitment_policies call is checked against it from then on.
Questions about list_commitment_policies
Cloud-agnostic PerfectScale for Commitments resources — commitment policies shared by AWS and GCP. Returns every commitment policy available to the tenant: the three built-in policies (conservative, balanced, max_savings) followed by the tenant's own custom policies. Commitment policies are cloud-agnostic. A single catalog is shared by AWS and GCP, and the same policy may be assigned to AWS and GCP product lines alike. Built-in policies are listed first, ordered from least to most aggressive target coverage; custom policies follow in creation order. Percentage parameters are expressed as 1–100, as entered in the DoiT Console. This differs from the coverage and utilization fields on recommendations and inventory, which are fractions from 0 to 1. This endpoint is read-only. Custom policies are created, edited and deleted in the DoiT Console on the Commitment Policies page. 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.
list_commitment_policies accepts 4 parameters: pageToken, maxResults, X-Tenant-Id, customerContext. 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 list_commitment_policies: 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.
list_commitment_policies 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 list_commitment_policies 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 list_commitment_policies. 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.
list_commitment_policies 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