get_experiment

[SUPPORT] 3f6b8715 — read one project-scoped experiment by id.

SERVERMeridian SOURCE@meridianmcp/mcp

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/get-experiment.md

WHAT IT DOES

What get_experiment does on Meridian

AI agents call get_experiment to retrieve information from Meridian without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`project_id`	string	—
`project_name`	string	—	Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given.
`experiment_id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why get_experiment is rated Low

Even though get_experiment only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_experiment safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Meridian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_experiment, this is the rule to start with:

get_experiment Allowed

get_experiment is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meridian, apply this rule, and every get_experiment call is checked against it from then on.

FAQ

Questions about get_experiment

What does the get_experiment tool do? +

[SUPPORT] 3f6b8715 — read one project-scoped experiment by id. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.

What parameters does get_experiment accept? +

get_experiment accepts 3 parameters: project_id, project_name, experiment_id. Required: experiment_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_experiment? +

Register the Meridian 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 Meridian. Nothing to install.

What risk level is get_experiment? +

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

Can I rate-limit get_experiment? +

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.

How do I block get_experiment completely? +

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.

What MCP server provides get_experiment? +

get_experiment is provided by the Meridian MCP server (@meridianmcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meridian, and thousands of servers like it.

This server

All 235 Meridian tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →