Get metadata for a single EBI Expression Atlas experiment by accession (e.g. "E-MTAB-4045"). Returns accession, description, species, type, assay count, and experimental factors.
AI agents call get_experiment to retrieve information from Expression Atlas without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
accession | string | Yes | Experiment accession, e.g. "E-MTAB-4045", "E-GEOD-61857". |
Parameters from the server's own tool schema.
This tool retrieves and queries existing gene expression experiment metadata from the EBI Expression Atlas without any side effects. It is purely informational—fetching metadata about a single experiment given an accession identifier. No data is created, modified, deleted, or executed.
From the tool's definition Tool returns metadata for an experiment by accession ID: 'accession, description, species, type, assay count, and experimental factors.' No mention of modification, deletion, or execution of operations.
Attacks that exploit this kind of access
Get metadata for a single EBI Expression Atlas experiment by accession (e.g. "E-MTAB-4045"). Returns accession, description, species, type, assay count, and experimental factors. It is categorised as a Read tool in the Expression Atlas MCP Server, which means it retrieves data without modifying state.
get_experiment accepts 1 parameter: accession. Required: accession. The full parameter table on this page comes from the server's own tool schema.
Register the Expression Atlas MCP server in PolicyLayer and add a rule for get_experiment: 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 Expression Atlas. Nothing to install.
get_experiment 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 get_experiment 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 get_experiment. 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.
get_experiment is provided by the Expression Atlas MCP server (https://gateway.pipeworx.io/expression-atlas/mcp). 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 →