Medium Risk

create_fhir_resource

Create a new FHIR resource in HealthLake

How to control create_fhir_resource ↓

What create_fhir_resource does on Awslabs Amazon Sns Sqs

AI agents use create_fhir_resource to create or update resources in Awslabs Amazon Sns Sqs — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Awslabs Amazon Sns Sqs environment.

Medium Risk

Why create_fhir_resource needs a policy

The tool creates (writes) new FHIR healthcare resources, which is a write operation. It is not destructive since FHIR resources can be deleted or updated. However, the severity is elevated to 'high' because healthcare data is sensitive and Protected Health Information (PHI); unauthorized creation could introduce false medical records, compromise patient care, or violate HIPAA compliance.

From the tool's definition Tool name contains 'create' and description states 'Create a new FHIR resource' - this is a reversible data creation operation that adds records to a healthcare system (HealthLake).

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

How to control create_fhir_resource

PolicyLayer is an MCP gateway — it sits between your AI agents and Awslabs Amazon Sns Sqs, and nothing reaches the server without passing your rules. This is the rule we recommend for create_fhir_resource:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_fhir_resource": {
      "limits": [
        {
          "counter": "create_fhir_resource_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Awslabs Amazon Sns Sqs — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about create_fhir_resource

What does the create_fhir_resource tool do? +

Create a new FHIR resource in HealthLake. It is categorised as a Write tool in the Awslabs Amazon Sns Sqs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_fhir_resource? +

Register the Awslabs Amazon Sns Sqs MCP server in PolicyLayer and add a rule for create_fhir_resource: 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 Awslabs Amazon Sns Sqs. Nothing to install.

What risk level is create_fhir_resource? +

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

Can I rate-limit create_fhir_resource? +

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

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

create_fhir_resource is provided by the Awslabs Amazon Sns Sqs MCP server (awslabs.amazon-sns-sqs-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 Awslabs Amazon Sns Sqs tool call.

Start from Awslabs Amazon Sns Sqs, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

805 Awslabs Amazon Sns Sqs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.