Submit a bulk dispense request for a patient's full medication list.
AI agents use create_dispense_request 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.
This tool creates new dispense requests (reversible via cancellation or correction workflows typical in pharmacy systems), affecting medication fulfillment but not immediately destroying data or executing arbitrary code.
From the tool's definition Tool name 'create_dispense_request' and description 'Submit a bulk dispense request' indicate creation of pharmacy dispensing records.
Attacks that exploit this kind of access
Submit a bulk dispense request for a patient's full medication list. 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.
Register the MCPDischarge MCP server in PolicyLayer and add a rule for create_dispense_request: 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.
create_dispense_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_dispense_request 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.
Set action: deny in the PolicyLayer policy for create_dispense_request. 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.
create_dispense_request 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →