Check availability at external/nearby pharmacies when local stock is out.
AI agents call check_nearby_pharmacy_availability to retrieve information from MCPDischarge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about pharmacy inventory at remote locations to support discharge coordination. It is a read-only query with no side effects: no data is modified, no orders are placed, and no financial transactions are initiated. The blast radius of misuse is minimal (information disclosure of public or semi-public pharmacy stock data).
From the tool's definition Tool description states it 'Check[s] availability at external/nearby pharmacies' — a pure query/lookup operation with no modification, deletion, or execution of external systems.
Attacks that exploit this kind of access
Check availability at external/nearby pharmacies when local stock is out. It is categorised as a Read tool in the MCPDischarge MCP Server, which means it retrieves data without modifying state.
Register the MCPDischarge MCP server in PolicyLayer and add a rule for check_nearby_pharmacy_availability: 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.
check_nearby_pharmacy_availability is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_nearby_pharmacy_availability 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 check_nearby_pharmacy_availability. 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.
check_nearby_pharmacy_availability 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 →