Preprocess a single-cell RNA-seq dataset: filter cells/genes, normalize, log-transform, and identify highly variable genes. Returns QC summary.
AI agents invoke preprocess_omics to trigger actions in MedSci Agent. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool performs a multi-step computational pipeline (filtering, normalization, log-transformation, HVG identification) on input data. It executes a sequence of data transformation operations rather than simply reading or writing discrete records. While it does not delete data irreversibly or move money, it actively runs processing logic that transforms datasets, placing it in the Execute category.
From the tool's definition Preprocess a single-cell RNA-seq dataset: filter cells/genes, normalize, log-transform, and identify highly variable genes
Documented attack patterns abuse exactly the kind of access preprocess_omics gives an agent:
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 preprocess_omics:
{
"version": "1",
"default": "deny",
"tools": {
"preprocess_omics": {
"limits": [
{
"counter": "preprocess_omics_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}preprocess_omics stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Preprocess a single-cell RNA-seq dataset: filter cells/genes, normalize, log-transform, and identify highly variable genes. Returns QC summary. It is categorised as a Execute tool in the MedSci Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MedSci Agent MCP server in PolicyLayer and add a rule for preprocess_omics: 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.
preprocess_omics is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the preprocess_omics 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 preprocess_omics. 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.
preprocess_omics 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.
Start from MedSci Agent, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
28 MedSci Agent tools catalogued and risk-classified — across an index of 43,000+ MCP servers.