create_encounter · athenahealth MCP Server MCP

WHAT IT DOES

What create_encounter does on athenahealth MCP Server

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

WHY IT NEEDS A POLICY

Why create_encounter needs a policy

This tool creates a new clinical encounter record, which is a Write operation (creates or modifies data reversibly). The severity is high because creating encounter records in a healthcare system has significant downstream effects: it may trigger billing, update patient history, generate documentation requirements, and influence clinical decision-making.

From the tool's definition Tool name is 'create_encounter' and description states 'Create a new encounter for a patient' — this creates a new clinical record that can be modified but is not inherently destructive. The tool creates/adds data reversibly within a healthcare system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_encounter Rate-limited

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

FAQ

Questions about create_encounter

What does the create_encounter tool do? +

Create a new encounter for a patient. It is categorised as a Write tool in the athenahealth 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 create_encounter? +

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

What risk level is create_encounter? +

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

Can I rate-limit create_encounter? +

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

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

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