List experiments under experiments/. With proposal_id,
AI agents call list_experiments to retrieve information from Ebony Enriching without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of experiments, which is a pure read operation with no side effects. The append-only semantics of the system and the tool's function to list data confirms it performs only data retrieval. No data is created, modified, deleted, or any external operations are triggered.
From the tool's definition Tool name is 'list_experiments' and description states 'List experiments under `experiments/`' — a retrieval operation with no modification capability.
Attacks that exploit this kind of access
List experiments under experiments/. With proposal_id,. It is categorised as a Read tool in the Ebony Enriching MCP Server, which means it retrieves data without modifying state.
Register the Ebony Enriching MCP server in PolicyLayer and add a rule for list_experiments: 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 Ebony Enriching. Nothing to install.
list_experiments 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 list_experiments 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 list_experiments. 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.
list_experiments is provided by the Ebony Enriching MCP server (parkviewlab/ebony-enriching). 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 →