create_partner
Create a partner relationship. partnerType is required (ISV_TECH, AI_LAB, HYPERSCALER, GSI_SI, RESELLER, MARKETPLACE, ADVISORY, REFERRAL, COMMUNITY). The authenticated user becomes owner unless ownerId is explicitly supplied. motions is an array of CO_SELL, RESELL, SELL_TO, BUILD_WITH, REFER.
This record as markdown: /tools/adrata-starfield-mcp/create-partner.md
What create_partner does on Starfield
AI agents use create_partner 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 |
|---|---|---|---|
name | string | Yes | |
tier | string | — | STRATEGIC, SELECT, MANAGED, LONGTAIL |
status | string | — | |
motions | array | — | |
ownerId | string | — | |
regions | array | — | |
website | string | — | |
industry | string | — | |
companyId | string | — | |
description | string | — | |
partnerType | string | Yes | |
commitmentAmount | number | — |
Parameters from the server's own tool schema.
Why create_partner is rated Medium
An AI agent can call create_partner 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.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs create_partner 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 create_partner, this is the rule to start with:
create_partner 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Starfield, apply this rule, and every create_partner call is checked against it from then on.
Questions about create_partner
Create a partner relationship. partnerType is required (ISV_TECH, AI_LAB, HYPERSCALER, GSI_SI, RESELLER, MARKETPLACE, ADVISORY, REFERRAL, COMMUNITY). The authenticated user becomes owner unless ownerId is explicitly supplied. motions is an array of CO_SELL, RESELL, SELL_TO, BUILD_WITH, REFER. 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.
create_partner accepts 12 parameters: name, tier, status, motions, ownerId, regions, website, industry, companyId, description, partnerType, commitmentAmount. Required: name, partnerType. The full parameter table on this page comes from the server's own tool schema.
Register the Starfield MCP server in PolicyLayer and add a rule for create_partner: 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.
create_partner is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_partner 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 create_partner. 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.
create_partner 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.
More on Starfield, and thousands of servers like it.
This server
Across the catalogue