Provides comprehensive guidance for evaluating whether code changes require feature flags. This tool returns detailed evaluation guidelines including: - Workflow for systematic evaluation - Parent flag detection patterns (avoid nesting) - Risk assessment criteria - Code type evaluation (test, con...
Part of the Unleash server.
Free to start. No card required.
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.
{
"version": "1",
"default": "deny",
"tools": {
"evaluate_change": {}
}
}See the full Unleash policy for all 13 tools.
These attack patterns abuse exactly the kind of access evaluate_change gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Provides comprehensive guidance for evaluating whether code changes require feature flags. This tool returns detailed evaluation guidelines including: - Workflow for systematic evaluation - Parent flag detection patterns (avoid nesting) - Risk assessment criteria - Code type evaluation (test, config, feature, etc.) - Decision tree logic - Best practices from Unleash documentation - MANDATORY next action instructions: Explicit tool call sequence (create_flag → wrap_change → implement) Use this tool when: - Starting work on a new feature or change - Unsure if a feature flag is needed - Want guidance on rollout strategy - Need help choosing flag type IMPORTANT WORKFLOW: When this tool determines a flag is needed, it provides explicit instructions to: 1. Call. It is categorised as a Read tool in the Unleash MCP Server, which means it retrieves data without modifying state.
Register the Unleash MCP server in PolicyLayer and add a rule for evaluate_change: 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 Unleash. Nothing to install.
evaluate_change 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 evaluate_change 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 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.
evaluate_change is provided by the Unleash MCP server (Unleash/unleash-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Unleash tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.