uploadDocument · Medical MCP Server MCP: Risk & Policy

WHAT IT DOES

What uploadDocument does on Medical MCP Server

AI agents use uploadDocument 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 uploadDocument needs a policy

This tool creates and stores medical documents and their processed outputs (embeddings, NER extractions) in the medical MCP system. While not destructive, uploading medical documents represents a Write operation with high severity due to the sensitive nature of medical data — an agent could upload inappropriate, false, or privacy-violating medical records that could affect patient care or violate HIPAA.

From the tool's definition Tool name is 'uploadDocument' and description states it will 'Upload and process a medical document' — this creates new data in the system (the uploaded document and its processed derivatives: extracted text, NER results, embeddings).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

uploadDocument Rate-limited

uploadDocument 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": {
    "uploadDocument": {
      "limits": [
        {
          "counter": "uploaddocument_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 uploadDocument

What does the uploadDocument tool do? +

Upload and process a medical document with automatic text extraction, BioClinical NER, and local embedding generation. 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 uploadDocument? +

Register the Medical MCP Server MCP server in PolicyLayer and add a rule for uploadDocument: 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 uploadDocument? +

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

Can I rate-limit uploadDocument? +

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

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

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