move_pipeline_card

Move a person/company/opportunity card on a pipeline board and publish a realtime event so the web app can update. Requires explicit approval, reason, and idempotencyKey.

SERVERStarfield SOURCE@adrata/starfield-mcp

Medium RISK CLASS

Category Write

Parameters 113 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/move-pipeline-card.md

WHAT IT DOES

What move_pipeline_card does on Starfield

AI agents use move_pipeline_card 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
`reason`	string	—
`userId`	string	—	User id for realtime attribution. Defaults to agent.
`approved`	boolean	—
`entityId`	string	Yes
`entityName`	string	—
`entityType`	string	Yes
`targetRank`	number	—
`targetStage`	string	Yes
`workspaceId`	string	—	Defaults to ADRATA_WORKSPACE_ID or CLI config workspace. Required for realtime fan-out.
`previousStage`	string	—
`idempotencyKey`	string	—

Parameters from the server's own tool schema.

RISK

Why move_pipeline_card is rated Medium

An AI agent can call move_pipeline_card 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 (11 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

move_pipeline_card Rate-limited

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

FAQ

Questions about move_pipeline_card

What does the move_pipeline_card tool do? +

Move a person/company/opportunity card on a pipeline board and publish a realtime event so the web app can update. Requires explicit approval, reason, and 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 move_pipeline_card accept? +

move_pipeline_card accepts 11 parameters: reason, userId, approved, entityId, entityName, entityType, targetRank, targetStage, workspaceId, previousStage, idempotencyKey. Required: entityId, entityType, targetStage. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on move_pipeline_card? +

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

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

Can I rate-limit move_pipeline_card? +

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

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

move_pipeline_card 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

move-task on Kanban MCP Server → The MCP Attack Database →

Guides

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