start_dicom_export_job

What start_dicom_export_job does on AWS

AI agents invoke start_dicom_export_job to trigger actions in AWS. 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.

Why start_dicom_export_job is rated High

The tool starts (initiates/triggers) a DICOM export job, which is a subprocess or async operation. This is characteristic of Execute-category tools: it runs an operation whose real-world effects depend on how the job is configured and where data flows. While not destructive by itself, misuse could export sensitive medical imaging data to unintended destinations, making it high-severity.

From the tool's definition Tool name is 'start_dicom_export_job' — a job-triggering action on AWS infrastructure. DICOM export operations involve initiating external processes/jobs whose effects depend on configuration arguments (destination, scope, filters).

The rule that runs start_dicom_export_job safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For start_dicom_export_job, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_dicom_export_job": {
      "limits": [
        {
          "counter": "start_dicom_export_job_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about start_dicom_export_job