List the quantitative target interactions for a drug ligand in the Guide to PHARMACOLOGY (IUPHAR/BPS). Given a GtoPdb ligand id (from search_ligands), returns the protein targets it acts on with interaction type (Agonist/Antagonist/Inhibitor/etc.), action, and binding affinity (e.g. pKi/pIC50). K...
AI agents call ligand_interactions to retrieve information from Guidetopharmacology without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max interactions to return (default 25). |
ligand_id | number | string | Yes | GtoPdb ligand id, e.g. 4139 for aspirin. |
Parameters from the server's own tool schema.
This tool purely retrieves pre-existing pharmacological data from a public database (IUPHAR/BPS Guide to PHARMACOLOGY). It performs a lookup/query operation with no side effects, no data modification, and no external command execution. The blast radius of misuse is minimal — an AI agent cannot cause harm by querying drug interaction information. This is a standard Read operation.
From the tool's definition Tool description explicitly states it 'List[s] the quantitative target interactions' and 'returns the protein targets it acts on' — retrieval and querying operations only. The term 'Keyless' confirms no authentication needed.
Attacks that exploit this kind of access
List the quantitative target interactions for a drug ligand in the Guide to PHARMACOLOGY (IUPHAR/BPS). Given a GtoPdb ligand id (from search_ligands), returns the protein targets it acts on with interaction type (Agonist/Antagonist/Inhibitor/etc.), action, and binding affinity (e.g. pKi/pIC50). Keyless. It is categorised as a Read tool in the Guidetopharmacology MCP Server, which means it retrieves data without modifying state.
ligand_interactions accepts 2 parameters: limit, ligand_id. Required: ligand_id. The full parameter table on this page comes from the server's own tool schema.
Register the Guidetopharmacology MCP server in PolicyLayer and add a rule for ligand_interactions: 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 Guidetopharmacology. Nothing to install.
ligand_interactions 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 ligand_interactions 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 ligand_interactions. 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.
ligand_interactions is provided by the Guidetopharmacology MCP server (pipeworx-io/mcp-guidetopharmacology). 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 →