start_fhir_import_job

WHAT IT DOES

What start_fhir_import_job does on AWS Labs Timestream for InfluxDB MCP Server

AI agents invoke start_fhir_import_job to trigger actions in AWS Labs Timestream for InfluxDB 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.

THE RISK

High Risk

Why start_fhir_import_job needs a policy

This tool triggers execution of a data import job into AWS HealthLake, an external service operation. While it performs data loading (which could be considered Write), the primary action is to initiate/execute a background job whose side effects depend on job parameters and data being imported. This is characteristic of Execute category (triggers external operations).

From the tool's definition Tool name 'start_fhir_import_job' and description 'Start a FHIR import job to load data into HealthLake' indicate triggering an external operation (import job) whose effects depend on the data source and target configuration arguments.

Documented attack patterns abuse exactly the kind of access start_fhir_import_job gives an agent:

POLICY

How to control start_fhir_import_job

PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Labs Timestream for InfluxDB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for start_fhir_import_job:

policy.json

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

start_fhir_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.

Create a free account and register AWS Labs Timestream for InfluxDB MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More AWS Labs Timestream for InfluxDB MCP Server tools

Destructive bulk_delete_by_criteria bulk_delete_by_criteria Destructive cache_delete Delete a value from the cache. Destructive cache_delete_many Delete multiple values from the cache. Destructive cache_delete_multi Delete multiple values from the cache (alias for delete_many). Destructive delete delete Destructive delete_access_key delete_access_key Destructive delete_agent_runtime delete_agent_runtime Destructive delete_agent_runtime_endpoint delete_agent_runtime_endpoint

All 805 AWS Labs Timestream for InfluxDB MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

Govern code and CI agents → Branch allowlists, approval on merges, and rate caps on the build and pipeline tools agents trigger.
High-risk tools in AWS Labs Timestream for InfluxDB MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

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 Execute tool in the AWS Labs Timestream for InfluxDB 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_fhir_import_job? +

Register the AWS Labs Timestream for InfluxDB 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 Labs Timestream for InfluxDB MCP Server. Nothing to install.

What risk level is start_fhir_import_job? +

start_fhir_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_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 Labs Timestream for InfluxDB MCP Server MCP server (awslabs.timestream-for-influxdb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AWS Labs Timestream for InfluxDB MCP Server tool call.

Start from AWS Labs Timestream for InfluxDB MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

805 AWS Labs Timestream for InfluxDB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.