list_aws_planned_purchases

SERVERDoit SOURCE@doitintl/doit-mcp-server

Low RISK CLASS

Category Read

Parameters 61 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/doit/list-aws-planned-purchases.md

WHAT IT DOES

What list_aws_planned_purchases does on Doit

AI agents call list_aws_planned_purchases 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
`service`	string	—
`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.
`managementAccountId`	string	Yes

Parameters from the server's own tool schema.

RISK

Why list_aws_planned_purchases is rated Low

Even though list_aws_planned_purchases 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_aws_planned_purchases 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_aws_planned_purchases, this is the rule to start with:

list_aws_planned_purchases Allowed

list_aws_planned_purchases 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_aws_planned_purchases": {}
  }
}

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_aws_planned_purchases call is checked against it from then on.

FAQ

Questions about list_aws_planned_purchases

What does the list_aws_planned_purchases tool do? +

Evaluate current AWS commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns planned purchases (laddering projections) for the AWS organization. One item per commitment type that has a projection available (typically compute and/or database; up to four commitment types as PerfectScale for Commitments expands). With no filters, returns all available planned-purchase items for the AWS organization in stable commitment-type order (compute, then database, then any future commitment types in enum order). When a filtered commitment type has no planned purchases, the response is an empty items array (not 404). Partial items return only the fields available at response time. 404 is returned only when the AWS organization does not exist or the caller cannot access it. An AWS organization that is not onboarded for PerfectScale for Commitments still returns 200 with an empty items array when no planned purchases exist — use GET /ps4commitments/v1/aws/organizations (or get-by-id) for onboardingStatus. Pagination: results are returned in stable commitment-type order (compute, then database, then any future commitment types in enum order). Use maxResults to limit page size (default 50, max 500). When more items remain, the response includes a non-null pageToken; pass it unchanged on the next request with the same query parameters (service, maxResults). rowCount is the number of items in this page. An invalid pageToken returns 400 with code pagination_token_invalid; an expired token returns 400 with code pagination_token_expired. 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_aws_planned_purchases accept? +

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

How do I enforce a policy on list_aws_planned_purchases? +

Register the Doit MCP server in PolicyLayer and add a rule for list_aws_planned_purchases: 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_aws_planned_purchases? +

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

Can I rate-limit list_aws_planned_purchases? +

Yes. Add a rate_limit block to the list_aws_planned_purchases 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_aws_planned_purchases completely? +

Set action: deny in the PolicyLayer policy for list_aws_planned_purchases. 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_aws_planned_purchases? +

list_aws_planned_purchases 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 →