start_dicom_import_job · AWS IoT SiteWise MCP Server MCP

WHAT IT DOES

What start_dicom_import_job does on AWS IoT SiteWise MCP Server

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

WHY IT NEEDS A POLICY

Why start_dicom_import_job needs a policy

Although the description is empty (lowering confidence slightly), the tool name and context indicate this tool starts an asynchronous job that executes an import operation. This is a side-effecting operation that initiates external processing and data ingestion. It does not delete or move money (ruling out Destructive/Financial), but it performs actions whose effects depend on arguments and configuration.

From the tool's definition Tool name 'start_dicom_import_job' indicates initiating an import operation with external side effects. The tool name strongly suggests triggering a DICOM (medical imaging) import process that would consume resources, process data, and potentially persist…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_dicom_import_job Rate-limited

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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches AWS IoT SiteWise MCP Server, so you can run agents against it safely.

FAQ

Questions about start_dicom_import_job

What does the start_dicom_import_job tool do? +

start_dicom_import_job. It is categorised as a Execute tool in the AWS IoT SiteWise 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_import_job? +

Register the AWS IoT SiteWise 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 IoT SiteWise MCP Server. Nothing to install.

What risk level is start_dicom_import_job? +

start_dicom_import_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_import_job? +

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.

How do I block start_dicom_import_job completely? +

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.

What MCP server provides start_dicom_import_job? +

start_dicom_import_job is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.