adrata_ai_tool_execute

SERVERStarfield SOURCE@adrata/starfield-mcp

High RISK CLASS

Category Execute

Parameters 81 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/adrata-ai-tool-execute.md

WHAT IT DOES

What adrata_ai_tool_execute does on Starfield

AI agents invoke adrata_ai_tool_execute 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
`dryRun`	boolean	—	Defaults to true for write tools. Set false only after explicit approval.
`reason`	string	—	Required audit reason for a spend acknowledgment or when requesting a live-write confirmation token.
`approved`	boolean	—	Deprecated compatibility field; never authorizes a live write.
`toolName`	string	Yes	AI CRM tool name from adrata_ai_tool_catalog, e.g. list_channels or rank_companies_by_icp
`arguments`	object	—
`confirmSpend`	boolean	—	Required true to execute a read held for external vendor spend. Never authorizes a workspace write.
`idempotencyKey`	string	—	Required with confirmSpend:true. Reuse the same key on retry; the API replays the first response instead of calling the paid provider twice.
`confirmationToken`	string	—	Single-use server token returned by the first live-write request; bound to the user, workspace, tool, and stored arguments.

Parameters from the server's own tool schema.

RISK

Why adrata_ai_tool_execute is rated High

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

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

adrata_ai_tool_execute Rate-limited

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

FAQ

Questions about adrata_ai_tool_execute

What does the adrata_ai_tool_execute tool do? +

Execute the same governed AI CRM ToolDispatcher path used by Adrata chat. Free reads run directly. Reads that can spend external data credits return a spend hold; execute one only with confirmSpend:true, a reason, and an idempotencyKey (reuse the same key on retry). The response includes the approved ceiling and an exact provider-reported receipt where available. Writes use a two-step, server-bound confirmationToken flow; a client approved boolean can never authorize a write. A non-interactive machine/OAuth principal (every MCP client) can preview writes but cannot complete one. 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 adrata_ai_tool_execute accept? +

adrata_ai_tool_execute accepts 8 parameters: dryRun, reason, approved, toolName, arguments, confirmSpend, idempotencyKey, confirmationToken. Required: toolName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on adrata_ai_tool_execute? +

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

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

Can I rate-limit adrata_ai_tool_execute? +

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

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

adrata_ai_tool_execute 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

claude_execute on Claude Bridge →execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

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