Retrieve bioactivity records from ChEMBL filtered by molecule_chembl_id and/or target_chembl_id; returns IC50/Ki/EC50 values, assay descriptions, and units.
AI agents call activities to retrieve information from Mcp Chembl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the ChEMBL database to fetch bioactivity records (IC50/Ki/EC50 values and assay descriptions). It has no parameters for creating, modifying, deleting, or executing operations—only filtering and retrieving existing data. The operation is read-only with no side effects, making it a classic Read category tool.
From the tool's definition Tool description states 'Retrieve bioactivity records' with filtering parameters and return of data values. The verb 'Retrieve' and the read-only nature of querying bioactivity data without modification confirm this is a data retrieval operation.
Attacks that exploit this kind of access
Retrieve bioactivity records from ChEMBL filtered by molecule_chembl_id and/or target_chembl_id; returns IC50/Ki/EC50 values, assay descriptions, and units. It is categorised as a Read tool in the Mcp Chembl MCP Server, which means it retrieves data without modifying state.
Register the Mcp Chembl MCP server in PolicyLayer and add a rule for activities: 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 Mcp Chembl. Nothing to install.
activities 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 activities 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 activities. 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.
activities is provided by the Mcp Chembl MCP server (pipeworx-io/mcp-chembl). 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 →