configure_sloan

SERVERStarfield SOURCE@adrata/starfield-mcp

Medium RISK CLASS

Category Write

Parameters 70 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/configure-sloan.md

WHAT IT DOES

What configure_sloan does on Starfield

AI agents use configure_sloan 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
`action`	string	—	Default 'check' (read-only)
`reason`	string	—	Audit reason (mutations only)
`userId`	string	—	For 'set_autonomy': target seller (defaults to the caller)
`approved`	boolean	—	Explicit user approval (mutations only)
`autoInherit`	boolean	—	Optionally set sloan.auto_inherit alongside enable/disable (ignored if absent in this build)
`autonomyMode`	string	—	Required for 'set_autonomy'
`idempotencyKey`	string	—	Idempotency key for mutations

Parameters from the server's own tool schema.

RISK

Why configure_sloan is rated Medium

An AI agent can call configure_sloan 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 signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

configure_sloan Rate-limited

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

FAQ

Questions about configure_sloan

What does the configure_sloan tool do? +

Configure Sloan for the workspace. action 'check' (default) is READ-ONLY: a prerequisites checklist (workspace flag, server kill-switch, connected Sloan mailbox, operational scheduling provider). Actions 'enable'/'disable' toggle the sloan.ea_loop flag and 'set_autonomy' sets a seller's default autonomy mode — admin/manager-gated server-side; pass approved=true with a reason for mutations. 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 configure_sloan accept? +

configure_sloan accepts 7 parameters: action, reason, userId, approved, autoInherit, autonomyMode, idempotencyKey. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on configure_sloan? +

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

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

Can I rate-limit configure_sloan? +

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

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

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