AWS HealthImaging MCP Server

39 tools. 19 can modify or destroy data without limits.

11 destructive tools with no built-in limits. Policy required.

Last updated:

19 can modify or destroy data
20 read-only
39 tools total
Read (20) Write / Execute (8) Destructive / Financial (11)

Destructive tools (bulk_delete_by_criteria, delete_datastore, delete_image_set) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (bulk_update_patient_metadata, copy_image_set, create_datastore) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (start_dicom_export_job, start_dicom_import_job) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

Deny destructive operations
bulk_delete_by_criteria:
  rules:
    - action: deny

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
bulk_update_patient_metadata:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
get_datastore:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Can an AI agent delete data through the AWS HealthImaging MCP Server MCP server? +

Yes. The AWS HealthImaging MCP Server server exposes 11 destructive tools including bulk_delete_by_criteria, delete_datastore, delete_image_set. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through AWS HealthImaging MCP Server? +

The AWS HealthImaging MCP Server server has 6 write tools including bulk_update_patient_metadata, copy_image_set, create_datastore. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the AWS HealthImaging MCP Server MCP server expose? +

39 tools across 4 categories: Destructive, Execute, Read, Write. 20 are read-only. 19 can modify, create, or delete data.

How do I add Intercept to my AWS HealthImaging MCP Server setup? +

One line change. Instead of running the AWS HealthImaging MCP Server server directly, prefix it with Intercept: intercept -c aws-healthimaging-mcp-server.yaml -- npx -y @awslabs.healthimaging-mcp-server. Download a pre-built policy from policylayer.com/policies/aws-healthimaging-mcp-server and adjust the limits to match your use case.

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

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.