Low Risk

list_evaluators

List all available evaluators from Scorable

How to control list_evaluators ↓

What list_evaluators does on Root Signals MCP Server

AI agents call list_evaluators 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.

Low Risk

Why list_evaluators needs a policy

This tool queries and returns information about available evaluators without modifying, creating, deleting, or executing any operations. It is a simple listing/retrieval function analogous to 'list' or 'get', which is characteristic of Read category tools. The blast radius is minimal since it only exposes metadata about evaluators.

From the tool's definition Tool name 'list_evaluators' and description 'List all available evaluators from Scorable' indicate a data retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access list_evaluators gives an agent:

How to control list_evaluators

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_evaluators:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_evaluators": {}
  }
}

list_evaluators is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Root Signals MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_evaluators

What does the list_evaluators tool do? +

List all available evaluators from Scorable. It is categorised as a Read tool in the Root Signals MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_evaluators? +

Register the Root Signals MCP Server MCP server in PolicyLayer and add a rule for list_evaluators: 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.

What risk level is list_evaluators? +

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

Can I rate-limit list_evaluators? +

Yes. Add a rate_limit block to the list_evaluators 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 list_evaluators completely? +

Set action: deny in the PolicyLayer policy for list_evaluators. 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 list_evaluators? +

list_evaluators 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.

Enforce policy on every Root Signals MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.