request_provider_action_execution

SERVERStarfield SOURCE@adrata/starfield-mcp

High RISK CLASS

Category Execute

Parameters 62 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/request-provider-action-execution.md

WHAT IT DOES

What request_provider_action_execution does on Starfield

AI agents invoke request_provider_action_execution 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
`scope`	string	—	Expected scope for the action. If omitted, the endpoint catalog scope is used when available.
`action`	string	Yes	Endpoint/action slug to request, for example campaigns_get_all or salesforce_contacts_update
`dryRun`	boolean	—	Defaults to true. Set false only when the user has explicitly approved a live execution request.
`inputs`	object	—	Action input payload. Secrets should be credential refs, never raw credentials.
`reason`	string	—	Business reason shown in audit logs and approval review
`provider`	string	Yes	Provider slug, for example heyreach, salesforce, hubspot, gmail, or a custom provider slug

Parameters from the server's own tool schema.

RISK

Why request_provider_action_execution is rated High

request_provider_action_execution 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 request_provider_action_execution 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 request_provider_action_execution, this is the rule to start with:

request_provider_action_execution Rate-limited

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

FAQ

Questions about request_provider_action_execution

What does the request_provider_action_execution tool do? +

Request a scoped provider action execution without registering every provider endpoint as a separate MCP tool. Defaults to dry-run and returns policy, scope, billing, risk, and approval requirements before any live request. 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 request_provider_action_execution accept? +

request_provider_action_execution accepts 6 parameters: scope, action, dryRun, inputs, reason, provider. Required: action, provider. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on request_provider_action_execution? +

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

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

Can I rate-limit request_provider_action_execution? +

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

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

request_provider_action_execution 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

http_request on 0sec →qt_trigger_action on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

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