AI agents invoke start_dicom_import_job to trigger actions in AWS Labs CloudTrail MCP Server. 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.
Starting a DICOM import job is an Execute action because it triggers an external operation (data ingestion) that cannot be trivially undone and whose effects depend on arguments (source location, target repository). The high severity reflects that medical imaging data is sensitive and unauthorized imports could compromise data integrity or expose PHI.
From the tool's definition Tool name 'start_dicom_import_job' indicates initiation of an asynchronous job that imports DICOM (medical imaging) data.
Documented attack patterns abuse exactly the kind of access start_dicom_import_job gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Labs CloudTrail MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for start_dicom_import_job:
{
"version": "1",
"default": "deny",
"tools": {
"start_dicom_import_job": {
"limits": [
{
"counter": "start_dicom_import_job_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} 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.
Free to start. No card required.
start_dicom_import_job. It is categorised as a Execute tool in the AWS Labs CloudTrail MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS Labs CloudTrail MCP Server 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 Labs CloudTrail MCP Server. 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 Labs CloudTrail MCP Server MCP server (awslabs.cloudtrail-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Labs CloudTrail MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 AWS Labs CloudTrail MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.