pharmgkb.pharmacology.drug_search
Search the PharmGKB curated drug/chemical database by name (e.g. warfarin, clopidogrel, tamoxifen, codeine). Returns PharmGKB ID, canonical name, trade names, generic names, drug types, SMILES, InChI, ATC code, ChEBI ID, DrugBank ID, and pediatric annotation flag. PharmGKB covers 3,000+ pharmacol...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/pharmgkb.pharmacology.drug-search.md
What pharmgkb.pharmacology.drug_search does on Apibase
AI agents call pharmgkb.pharmacology.drug_search to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Drug or chemical name to search for (e.g. warfarin, clopidogrel, tamoxifen, codeine). Searches PharmGKB curated database of 3,000+ pharmacologically relevant co |
Parameters from the server's own tool schema.
Why pharmgkb.pharmacology.drug_search is rated Low
Tool retrieves drug information without modifying data, creating side effects, or enabling destructive actions.
From the tool's definition Search the PharmGKB curated drug/chemical database by name. Returns PharmGKB ID, canonical name, trade names.
Attacks that exploit this kind of access
The rule that runs pharmgkb.pharmacology.drug_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pharmgkb.pharmacology.drug_search, this is the rule to start with:
pharmgkb.pharmacology.drug_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every pharmgkb.pharmacology.drug_search call is checked against it from then on.
Questions about pharmgkb.pharmacology.drug_search
Search the PharmGKB curated drug/chemical database by name (e.g. warfarin, clopidogrel, tamoxifen, codeine). Returns PharmGKB ID, canonical name, trade names, generic names, drug types, SMILES, InChI, ATC code, ChEBI ID, DrugBank ID, and pediatric annotation flag. PharmGKB covers 3,000+ pharmacologically relevant compounds with PGx relationships. Source: PharmGKB, CC BY-SA 4.0. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
pharmgkb.pharmacology.drug_search accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for pharmgkb.pharmacology.drug_search: 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 Apibase. Nothing to install.
pharmgkb.pharmacology.drug_search 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 pharmgkb.pharmacology.drug_search 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 pharmgkb.pharmacology.drug_search. 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.
pharmgkb.pharmacology.drug_search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue