Validate whether two drugs are clinically therapeutically equivalent.
AI agents call check_therapeutic_equivalence 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 queries clinical drug equivalence data to provide validation results. It retrieves or compares information without creating, modifying, deleting, or executing operations that alter system state or trigger external actions. The output informs clinical decision-making but does not execute prescriptions, dispense medications, or commit financial transactions.
From the tool's definition Tool name contains 'check' and description states 'Validate whether two drugs are clinically therapeutically equivalent' — a purely informational lookup operation with no data modification, deletion, or external side effects.
Attacks that exploit this kind of access
Validate whether two drugs are clinically therapeutically equivalent. 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_therapeutic_equivalence: 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_therapeutic_equivalence 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_therapeutic_equivalence 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_therapeutic_equivalence. 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_therapeutic_equivalence 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 →