This record as markdown: /tools/aws/start-dicom-import-job.md
What start_dicom_import_job does on AWS
AI agents invoke start_dicom_import_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_import_job is rated High
This is an Execute-category tool because it triggers an asynchronous import operation whose actual side effects—data ingestion, processing, storage—depend on job parameters and external state.
From the tool's definition Tool name 'start_dicom_import_job' indicates it initiates a job that imports DICOM medical imaging data. The 'start' verb signals triggering an external operation whose effects depend on runtime arguments and configuration.
Attacks that exploit this kind of access
The rule that runs start_dicom_import_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_import_job, this is the rule to start with:
start_dicom_import_job 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.
The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every start_dicom_import_job call is checked against it from then on.
Questions about start_dicom_import_job
start_dicom_import_job is a execute tool on the AWS MCP server. It is categorised as a Execute tool in the AWS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS MCP server in PolicyLayer and add a rule for start_dicom_import_job: 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 AWS. Nothing to install.
start_dicom_import_job is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_dicom_import_job 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.
Set action: deny in the PolicyLayer policy for start_dicom_import_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.
start_dicom_import_job is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AWS, and thousands of servers like it.
This server
Across the catalogue