Check stock for multiple drugs in one call.
AI agents call check_bulk_stock 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 performs a read-only inventory lookup across multiple drugs. It queries existing stock information but does not create, modify, delete, or execute any operations. The sibling tools in the server (check_stock, check_dose_validity, check_nearby_pharmacy_availability) follow the same read-only pattern. Even in a healthcare context with potential PHI, stock levels are administrative data, not patient-sensitive.
From the tool's definition Tool name 'check_bulk_stock' and description 'Check stock for multiple drugs in one call' indicate a query operation that retrieves inventory data without modification.
Attacks that exploit this kind of access
Check stock for multiple drugs in one call. 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_bulk_stock: 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_bulk_stock 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_bulk_stock 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_bulk_stock. 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_bulk_stock 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 →