chembl.targets.search
Search for biological drug targets (proteins, enzymes, receptors, ion channels) in the ChEMBL database by name, target type, and source organism. Returns target ChEMBL ID, preferred name, target classification (SINGLE PROTEIN, PROTEIN COMPLEX, PROTEIN FAMILY, etc.), organism, UniProt accession nu...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/chembl.targets.search.md
What chembl.targets.search does on Apibase
AI agents call chembl.targets.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 |
|---|---|---|---|
limit | integer | — | Number of results to return (1–25, default 10). |
query | string | — | Biological target name to search (case-insensitive substring match). Examples: "Acetylcholinesterase", "Epidermal growth factor receptor", "COX-2". Omit to brow |
organism | string | — | Filter by source organism (case-insensitive substring match). Examples: "Homo sapiens", "Rattus norvegicus", "Escherichia coli". |
target_type | string | — | Filter by target classification. SINGLE PROTEIN is the most common for drug targets. PROTEIN COMPLEX for multi-subunit targets. |
Parameters from the server's own tool schema.
Why chembl.targets.search is rated Low
Tool retrieves publicly available drug target metadata without modifying data or triggering external operations.
From the tool's definition Search for biological drug targets. Returns target ChEMBL ID, preferred name, classification, organism.
Attacks that exploit this kind of access
The rule that runs chembl.targets.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 chembl.targets.search, this is the rule to start with:
chembl.targets.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 chembl.targets.search call is checked against it from then on.
Questions about chembl.targets.search
Search for biological drug targets (proteins, enzymes, receptors, ion channels) in the ChEMBL database by name, target type, and source organism. Returns target ChEMBL ID, preferred name, target classification (SINGLE PROTEIN, PROTEIN COMPLEX, PROTEIN FAMILY, etc.), organism, UniProt accession numbers, and gene symbols. Use returned target_chembl_id with chembl.activity.bioactivity to retrieve all compounds tested against a target and their potency values. ChEMBL covers 18,500+ targets from 650+ organisms. Source: EMBL-EBI ChEMBL — CC BY-SA 3.0, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
chembl.targets.search accepts 4 parameters: limit, query, organism, target_type. 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 chembl.targets.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.
chembl.targets.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 chembl.targets.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 chembl.targets.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.
chembl.targets.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