Low Risk

evaluate_change

Score risk and recommend feature flag usage

Part of the Unleash MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@unleash/mcp Read Risk 2/5

AI agents call evaluate_change to retrieve information from Unleash without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though evaluate_change only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-getunleash-unleash-mcp.yaml
tools:
  evaluate_change:
    rules:
      - action: allow

See the full Unleash policy for all 9 tools.

Tool Name evaluate_change
Category Read
MCP Server Unleash MCP Server
Risk Level Low

View all 9 tools →

Agents calling read-class tools like evaluate_change have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the evaluate_change tool do? +

Score risk and recommend feature flag usage. It is categorised as a Read tool in the Unleash MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on evaluate_change? +

Add a rule in your Intercept YAML policy under the tools section for evaluate_change. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Unleash MCP server.

What risk level is evaluate_change? +

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

Can I rate-limit evaluate_change? +

Yes. Add a rate_limit block to the evaluate_change rule in your Intercept 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 evaluate_change completely? +

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

evaluate_change is provided by the Unleash MCP server (@unleash/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Unleash

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.