parse_clinical_document · Fhir Synthetic MCP: Risk & Policy

WHAT IT DOES

What parse_clinical_document does on Fhir Synthetic

AI agents invoke parse_clinical_document to trigger actions in Fhir Synthetic. 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 parse_clinical_document needs a policy

parse_clinical_document triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

parse_clinical_document Rate-limited

parse_clinical_document 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": {
    "parse_clinical_document": {
      "limits": [
        {
          "counter": "parse_clinical_document_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 Fhir Synthetic, so you can run agents against it safely.

FAQ

Questions about parse_clinical_document

What does the parse_clinical_document tool do? +

parse_clinical_document. It is categorised as a Execute tool in the Fhir Synthetic MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on parse_clinical_document? +

Register the Fhir Synthetic MCP server in PolicyLayer and add a rule for parse_clinical_document: 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 Fhir Synthetic. Nothing to install.

What risk level is parse_clinical_document? +

parse_clinical_document is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit parse_clinical_document? +

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

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

parse_clinical_document is provided by the Fhir Synthetic MCP server (krishnakakani-github/fhir-synthetic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.