start_fhir_import_job · AWS DynamoDB MCP Server MCP

WHAT IT DOES

What start_fhir_import_job does on AWS DynamoDB MCP Server

AI agents use start_fhir_import_job to create or update resources in AWS DynamoDB MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS DynamoDB MCP Server environment.

WHY IT NEEDS A POLICY

Why start_fhir_import_job needs a policy

This tool loads data into AWS HealthLake by starting a FHIR import job. It creates/writes new data into the system, which is a Write operation. Severity is high because it can bulk-import large volumes of sensitive health records (FHIR data) into a production data store, potentially overwriting or polluting existing records. It is reversible in principle (data can be deleted), so it doesn't qualify as Destructive.

From the tool's definition 'Start a FHIR import job to load data into HealthLake' — initiates a data import/load operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_fhir_import_job Rate-limited

start_fhir_import_job stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_fhir_import_job": {
      "limits": [
        {
          "counter": "start_fhir_import_job_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 DynamoDB MCP Server, so you can run agents against it safely.

FAQ

Questions about start_fhir_import_job

What does the start_fhir_import_job tool do? +

Start a FHIR import job to load data into HealthLake. It is categorised as a Write tool in the AWS DynamoDB MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on start_fhir_import_job? +

Register the AWS DynamoDB MCP Server MCP server in PolicyLayer and add a rule for start_fhir_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 DynamoDB MCP Server. Nothing to install.

What risk level is start_fhir_import_job? +

start_fhir_import_job is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit start_fhir_import_job? +

Yes. Add a rate_limit block to the start_fhir_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_fhir_import_job completely? +

Set action: deny in the PolicyLayer policy for start_fhir_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_fhir_import_job? +

start_fhir_import_job is provided by the AWS DynamoDB MCP Server MCP server (awslabs.dynamodb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.