get_dicom_export_job

Get information about a DICOM export job.

Part of the AWS HealthImaging MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

awslabs.healthimaging-mcp-server Read

// WHEN AI AGENTS USE THIS TOOL

AI agents call get_dicom_export_job to retrieve information from AWS HealthImaging MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON GET_DICOM_EXPORT_JOB

Even though get_dicom_export_job only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

aws-healthimaging-mcp-server.yaml

tools:
  get_dicom_export_job:
    rules:
      - action: allow

See the full AWS HealthImaging MCP Server policy for all 39 tools.

// DETAILS

Tool Name get_dicom_export_job

Category Read

MCP Server AWS HealthImaging MCP Server MCP Server

Risk Level Low

// MORE AWS HEALTHIMAGING MCP SERVER TOOLS

Destructive bulk_delete_by_criteria Destructive delete_datastore Destructive delete_image_set Destructive delete_instance_in_series Destructive delete_instance_in_study Destructive delete_patient_studies Destructive delete_series_by_uid Destructive delete_study

View all 39 tools →

// WHAT CAN GO WRONG

Agents calling read-class tools like get_dicom_export_job have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Firecrawl Web Scraping Server firecrawl_check_crawl_status Firecrawl Web Scraping Server firecrawl_crawl Firecrawl Web Scraping Server firecrawl_deep_research Firecrawl Web Scraping Server firecrawl_extract Firecrawl Web Scraping Server firecrawl_map Firecrawl Web Scraping Server firecrawl_scrape

// RELATED READING

// FAQ

What does the get_dicom_export_job tool do? +

Get information about a DICOM export job.. It is categorised as a Read tool in the AWS HealthImaging MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_dicom_export_job? +

Add a rule in your Intercept YAML policy under the tools section for get_dicom_export_job. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS HealthImaging MCP Server MCP server.

What risk level is get_dicom_export_job? +

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

Can I rate-limit get_dicom_export_job? +

Yes. Add a rate_limit block to the get_dicom_export_job rule in your Intercept 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 get_dicom_export_job completely? +

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

get_dicom_export_job is provided by the AWS HealthImaging MCP Server MCP server (awslabs.healthimaging-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

get_dicom_export_job

Let agents act without letting them run wild.