AI agents call list-annotation-configs to retrieve information from Phoenix without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' prefix strongly suggests this tool retrieves or enumerates annotation configurations without side effects. Despite the empty description limiting certainty, the naming convention and context among sibling tools (which include get-dataset, get-dataset-examples, analyze_stock, etc.) indicates this is a retrieval operation.
From the tool's definition Tool name is 'list-annotation-configs' which indicates retrieval/listing of configuration data. The verb 'list' is characteristic of read operations that query and return data without modification.
Documented attack patterns abuse exactly the kind of access list-annotation-configs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Phoenix, and nothing reaches the server without passing your rules. This is the rule we recommend for list-annotation-configs:
{
"version": "1",
"default": "deny",
"tools": {
"list-annotation-configs": {}
}
}list-annotation-configs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
list-annotation-configs. It is categorised as a Read tool in the Phoenix MCP Server, which means it retrieves data without modifying state.
Register the Phoenix MCP server in PolicyLayer and add a rule for list-annotation-configs: 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 Phoenix. Nothing to install.
list-annotation-configs 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-annotation-configs 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-annotation-configs. 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-annotation-configs is provided by the Phoenix MCP server (@Arize-ai/phoenix). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 34 Phoenix tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
34 Phoenix tools catalogued and risk-classified — across an index of 42,500+ MCP servers.