lipinski_filter

THE RISK

Low Risk

Why lipinski_filter needs a policy

This is a read-only operation that analyzes and evaluates molecular properties to determine drug-likeness. It retrieves/queries computed results about an input molecule without side effects. The tool does not execute arbitrary code, make financial transactions, or modify any persistent state. Confidence is high due to the descriptive name and clear analytical purpose in the drug discovery context.

From the tool's definition Tool name is 'lipinski_filter' with description 'Check if a molecule passes Lipinski' — this performs a computational check/evaluation of molecular properties against Lipinski's Rule of Five criteria.

Documented attack patterns abuse exactly the kind of access lipinski_filter gives an agent:

POLICY

How to control lipinski_filter

PolicyLayer is an MCP gateway — it sits between your AI agents and MedSci Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for lipinski_filter:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lipinski_filter": {}
  }
}

lipinski_filter is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register MedSci Agent — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MedSci Agent tools

Destructive sandbox_teardown Stop or remove a Docker sandbox. By default only stops; set remove to true to also delete. Execute differential_expression Run differential expression analysis between cell groups. Identifies genes that are signif Execute sandbox_run_job Execute a command in an existing Docker sandbox and capture stdout, stderr, exit code, dur Execute cluster_cells Cluster cells in a preprocessed single-cell dataset using Leiden or Louvain community dete Execute preprocess_omics Preprocess a single-cell RNA-seq dataset: filter cells/genes, normalize, log-transform, an Execute sandbox_prepare Create or verify an isolated Docker sandbox for the workspace. Optionally apply a containe Read parse_fasta Parse a FASTA file and return sequence metadata: IDs, names, descriptions, lengths, and se Read acquire_documents Acquire policy-compliant scientific document text from DOI/PMID/PMCID/URL targets with pro

All 28 MedSci Agent tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about lipinski_filter

What does the lipinski_filter tool do? +

Check if a molecule passes Lipinski. It is categorised as a Read tool in the MedSci Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lipinski_filter? +

Register the MedSci Agent MCP server in PolicyLayer and add a rule for lipinski_filter: 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 MedSci Agent. Nothing to install.

What risk level is lipinski_filter? +

lipinski_filter is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit lipinski_filter? +

Yes. Add a rate_limit block to the lipinski_filter 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.

How do I block lipinski_filter completely? +

Set action: deny in the PolicyLayer policy for lipinski_filter. 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.

What MCP server provides lipinski_filter? +

lipinski_filter is provided by the MedSci Agent MCP server (omar-a-hassan/medsci-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MedSci Agent tool call.

Start from MedSci Agent, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →