syncDocumentToAidbox · Medical MCP Server MCP: Risk & Policy

WHAT IT DOES

What syncDocumentToAidbox does on Medical MCP Server

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

WHY IT NEEDS A POLICY

Why syncDocumentToAidbox needs a policy

This tool creates new medical records in Aidbox (a FHIR-compliant healthcare data platform) based on document extraction. While reversible through deletion, creating medical records represents a Write action with high severity due to the sensitive nature of healthcare data—unauthorized creation of patient records could compromise patient privacy, alter medical histories, or create false medical documentation.

From the tool's definition The tool description explicitly states it will 'create corresponding FHIR resources in Aidbox', which involves creating and persisting data in an external medical system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

syncDocumentToAidbox Rate-limited

syncDocumentToAidbox 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": {
    "syncDocumentToAidbox": {
      "limits": [
        {
          "counter": "syncdocumenttoaidbox_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 Medical MCP Server, so you can run agents against it safely.

FAQ

Questions about syncDocumentToAidbox

What does the syncDocumentToAidbox tool do? +

Extract medical information from uploaded document and create corresponding FHIR resources in Aidbox via MCP. It is categorised as a Write tool in the Medical 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 syncDocumentToAidbox? +

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

What risk level is syncDocumentToAidbox? +

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

Can I rate-limit syncDocumentToAidbox? +

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

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

syncDocumentToAidbox is provided by the Medical MCP Server MCP server (kalyankumarkonduru/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.