List all available judges from Scorable. Judge is a collection of evaluators forming LLM-as-a-judge.
AI agents call list_judges to retrieve information from Root Signals MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation to enumerate available judges. It has no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions. The blast radius of misuse is minimal—an agent can only discover what judges exist, not affect system state or trigger unintended operations.
From the tool's definition Tool name 'list_judges' and description 'List all available judges' indicate a retrieval/query operation that returns information about available judges without modifying any state or triggering external operations.
Documented attack patterns abuse exactly the kind of access list_judges gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Root Signals MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_judges:
{
"version": "1",
"default": "deny",
"tools": {
"list_judges": {}
}
}list_judges 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 all available judges from Scorable. Judge is a collection of evaluators forming LLM-as-a-judge. It is categorised as a Read tool in the Root Signals MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Root Signals MCP Server MCP server in PolicyLayer and add a rule for list_judges: 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 Root Signals MCP Server. Nothing to install.
list_judges 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_judges 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_judges. 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_judges is provided by the Root Signals MCP Server MCP server (root-signals/scorable-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Root Signals MCP Server, 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.
6 Root Signals MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.