High Risk →

start_dicom_export_job

Start a DICOM export job.

High parameter count (10 properties)

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

AI agents invoke start_dicom_export_job to trigger processes or run actions in AWS HealthImaging MCP Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

start_dicom_export_job can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

aws-healthimaging-mcp-server.yaml
tools:
  start_dicom_export_job:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

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

Tool Name start_dicom_export_job
Category Execute
Risk Level High

View all 39 tools →

Agents calling execute-class tools like start_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 tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

start_dicom_export_job is one of the high-risk operations in AWS HealthImaging MCP Server. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the start_dicom_export_job tool do? +

Start a DICOM export job.. It is categorised as a Execute tool in the AWS HealthImaging MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_dicom_export_job? +

Add a rule in your Intercept YAML policy under the tools section for start_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 start_dicom_export_job? +

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

Can I rate-limit start_dicom_export_job? +

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

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

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

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.