check_batch_import_status

Check progress for Adrata bulk imports created by external catalog, Channel, CSV, or bulk create flows.

SERVERStarfield SOURCE@adrata/starfield-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/check-batch-import-status.md

WHAT IT DOES

What check_batch_import_status does on Starfield

AI agents call check_batch_import_status to retrieve information from Starfield without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`batchId`	string	Yes

Parameters from the server's own tool schema.

RISK

Why check_batch_import_status is rated Low

Even though check_batch_import_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

check_batch_import_status Allowed

check_batch_import_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_batch_import_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Starfield, apply this rule, and every check_batch_import_status call is checked against it from then on.

FAQ

Questions about check_batch_import_status

What does the check_batch_import_status tool do? +

Check progress for Adrata bulk imports created by external catalog, Channel, CSV, or bulk create flows. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.

What parameters does check_batch_import_status accept? +

check_batch_import_status accepts 1 parameter: batchId. Required: batchId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on check_batch_import_status? +

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

check_batch_import_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_batch_import_status? +

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

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

check_batch_import_status 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

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →