start_fhir_export_job · Amazon MQ MCP Server MCP

WHAT IT DOES

What start_fhir_export_job does on Amazon MQ MCP Server

AI agents invoke start_fhir_export_job to trigger actions in Amazon MQ 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_fhir_export_job needs a policy

This tool initiates an asynchronous job that performs a significant data export operation. While exporting data itself is not destructive, triggering a job that extracts potentially sensitive healthcare data (FHIR) from HealthLake is an Execute-category action because it launches an external operation with side effects that depend on how the job is configured.

From the tool's definition The tool name and description indicate it 'Start[s] a FHIR export job to export data from HealthLake', which triggers an external operation (a data export job) whose effects depend on runtime arguments such as export scope, filters, and destination.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_fhir_export_job Rate-limited

start_fhir_export_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_fhir_export_job": {
      "limits": [
        {
          "counter": "start_fhir_export_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 Amazon MQ MCP Server, so you can run agents against it safely.

FAQ

Questions about start_fhir_export_job

What does the start_fhir_export_job tool do? +

Start a FHIR export job to export data from HealthLake. It is categorised as a Execute tool in the Amazon MQ 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_export_job? +

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

What risk level is start_fhir_export_job? +

start_fhir_export_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_export_job? +

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

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

start_fhir_export_job is provided by the Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.