approve_partner_attribution

SERVERStarfield SOURCE@adrata/starfield-mcp

Medium RISK CLASS

Category Write

Parameters 51 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What approve_partner_attribution does on Starfield

AI agents use approve_partner_attribution to create or update resources in Starfield, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Starfield environment.

Parameter	Type	Required	Description
`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.
`auditReason`	string	—	Required (non-empty) for live execution: why this write is happening. Stored for audit.
`attributionId`	string	Yes
`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.

Parameters from the server's own tool schema.

RISK

Why approve_partner_attribution is rated Medium

An AI agent can call approve_partner_attribution faster than any human can review: one bad instruction and it creates or modifies resources in Starfield by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

approve_partner_attribution Rate-limited

approve_partner_attribution stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "approve_partner_attribution": {
      "limits": [
        {
          "counter": "approve_partner_attribution_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about approve_partner_attribution

What does the approve_partner_attribution tool do? +

Approve a partner attribution (finance/ops sign-off). Writes an immutable audit row so strategic revenue stays defensible. 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 Write tool in the Starfield MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does approve_partner_attribution accept? +

approve_partner_attribution accepts 5 parameters: dryRun, approved, auditReason, attributionId, idempotencyKey. Required: attributionId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on approve_partner_attribution? +

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

approve_partner_attribution is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit approve_partner_attribution? +

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

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

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

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →