confirm_dispense · MCPDischarge MCP: Risk & Policy

WHAT IT DOES

What confirm_dispense does on MCPDischarge

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

WHY IT NEEDS A POLICY

Why confirm_dispense needs a policy

This tool records/confirms a dispensing event — it creates or modifies a record indicating medicines were issued. This is a Write operation (updating dispense status in EHR/Pharmacy system). It is reversible in principle (the record could be corrected), so it does not rise to Destructive. However, misuse could result in incorrect medication records affecting patient safety, warranting medium severity.

From the tool's definition Confirm that medicines have been issued to the patient

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

confirm_dispense Rate-limited

confirm_dispense 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": {
    "confirm_dispense": {
      "limits": [
        {
          "counter": "confirm_dispense_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 MCPDischarge, so you can run agents against it safely.

FAQ

Questions about confirm_dispense

What does the confirm_dispense tool do? +

Confirm that medicines have been issued to the patient. It is categorised as a Write tool in the MCPDischarge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on confirm_dispense? +

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

What risk level is confirm_dispense? +

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

Can I rate-limit confirm_dispense? +

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

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

confirm_dispense is provided by the MCPDischarge MCP server (prashantsingh1234/mcp_project). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.