Check if a drug name exists in the pharmacy formulary.
AI agents call validate_drug_name 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.
The tool retrieves information from the pharmacy formulary to confirm drug name validity. This is a straightforward read-only query with no side effects. Misuse risk is minimal even if an agent submits invalid or malicious drug names, as the operation only returns confirmatory data without triggering prescriptions, dispensing, or financial transactions. Severity is low due to limited blast radius.
From the tool's definition Tool performs a 'Check' operation to validate whether a drug name exists in the pharmacy formulary—a lookup/query function with no data modification, creation, deletion, or code execution.
Attacks that exploit this kind of access
Check if a drug name exists in the pharmacy formulary. 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 validate_drug_name: 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.
validate_drug_name 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 validate_drug_name 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 validate_drug_name. 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.
validate_drug_name 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 →