build_pursuit_command_center

SERVERStarfield SOURCE@adrata/starfield-mcp

High RISK CLASS

Category Execute

Parameters 80 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/build-pursuit-command-center.md

WHAT IT DOES

What build_pursuit_command_center does on Starfield

AI agents invoke build_pursuit_command_center 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
`reason`	string	—	Required audit reason when requesting an approved persistence operation.
`companyId`	string	—	Company/account ID. Supply this or companyName.
`companyName`	string	—	Company/account name when the ID is not known.
`buyerGroupId`	string	—	Optional buyer-room/group ID.
`opportunityId`	string	—	Optional opportunity/deal ID; otherwise Adrata selects the newest active account opportunity.
`persistArtifact`	boolean	—	Persist the versioned Pursuit artifact after explicit approval. Defaults to false.
`persistSequence`	boolean	—	Persist the proposed cadence after explicit approval; never enrolls recipients. Defaults to false.
`confirmationToken`	string	—	Single-use server token returned by the first persistence request.

Parameters from the server's own tool schema.

RISK

Why build_pursuit_command_center is rated High

build_pursuit_command_center 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

build_pursuit_command_center Rate-limited

build_pursuit_command_center 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": {
    "build_pursuit_command_center": {
      "limits": [
        {
          "counter": "build_pursuit_command_center_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 build_pursuit_command_center call is checked against it from then on.

FAQ

Questions about build_pursuit_command_center

What does the build_pursuit_command_center tool do? +

Build or refresh Adrata’s persistent, evidence-linked Pursuit command center for one enterprise account. Composes the active opportunity, structured MEDDPICC, buyer room and path to power, deal health and forecast risk, triggers, one recommended Give/Get move, and reviewable email/cadence proposals. Preview is non-mutating by default. Persisting the artifact or cadence requires the server-issued confirmation flow, an audit reason, and idempotent governed execution. 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 build_pursuit_command_center accept? +

build_pursuit_command_center accepts 8 parameters: reason, companyId, companyName, buyerGroupId, opportunityId, persistArtifact, persistSequence, confirmationToken. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on build_pursuit_command_center? +

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

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

Can I rate-limit build_pursuit_command_center? +

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

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

build_pursuit_command_center 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

adb_shell_command on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

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