record_partner_consumption

SERVERStarfield SOURCE@adrata/starfield-mcp

High RISK CLASS

Category Execute

Parameters 121 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/record-partner-consumption.md

WHAT IT DOES

What record_partner_consumption does on Starfield

AI agents invoke record_partner_consumption to trigger actions in Starfield. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`notes`	string	—
`driver`	string	—
`dryRun`	boolean	—	Defaults to TRUE: returns a preview of the exact write (payload + endpoint) without executing. Set false to execute live.
`approved`	boolean	—	Required true for live execution — explicit approval of this specific money write.
`companyId`	string	—
`partnerId`	string	Yes
`auditReason`	string	—	Required (non-empty) for live execution: why this write is happening. Stored for audit.
`periodLabel`	string	—	e.g. 2026-Q3, FY26
`opportunityId`	string	—
`consumedAmount`	number	—
`idempotencyKey`	string	—	Required for live execution: unique key (e.g. a ULID) sent as the Idempotency-Key header. Reuse the SAME key on retry so the write cannot double-book.
`committedAmount`	number	—

Parameters from the server's own tool schema.

RISK

Why record_partner_consumption is rated High

record_partner_consumption triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signalsHigh parameter count (12 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs record_partner_consumption safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Starfield, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For record_partner_consumption, this is the rule to start with:

record_partner_consumption Rate-limited

record_partner_consumption stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "record_partner_consumption": {
      "limits": [
        {
          "counter": "record_partner_consumption_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about record_partner_consumption

What does the record_partner_consumption tool do? +

Record committed vs consumed revenue for a partner over a period. Signature != revenue: in a consumption business revenue is realized as usage grows, and partners drive it. driver: services_delivery, marketplace, self_serve, center_of_excellence. MONEY WRITE: dry-run by default (returns a preview); live execution requires approved:true, a non-empty auditReason, and an idempotencyKey. It is categorised as a Execute tool in the Starfield MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does record_partner_consumption accept? +

record_partner_consumption accepts 12 parameters: notes, driver, dryRun, approved, companyId, partnerId, auditReason, periodLabel, opportunityId, consumedAmount, idempotencyKey, committedAmount. Required: partnerId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on record_partner_consumption? +

Register the Starfield MCP server in PolicyLayer and add a rule for record_partner_consumption: 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 Starfield. Nothing to install.

What risk level is record_partner_consumption? +

record_partner_consumption is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit record_partner_consumption? +

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

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

record_partner_consumption is provided by the Starfield MCP server (@adrata/starfield-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Starfield, and thousands of servers like it.

This server

All 233 Starfield tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →