Get the log of past evolution runs from this session. Returns a list of all evolution runs with their results, including graduated strategies, graveyard, token usage, and backtest counts. Data is in-memory (resets on server restart).
Part of the Tradememory Protocol MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call evolution_get_log to retrieve information from Tradememory Protocol 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 evolution_get_log 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.
tools:
evolution_get_log:
rules:
- action: allowSee the full Tradememory Protocol policy for all 15 tools.
Agents calling read-class tools like evolution_get_log have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get the log of past evolution runs from this session. Returns a list of all evolution runs with their results, including graduated strategies, graveyard, token usage, and backtest counts. Data is in-memory (resets on server restart).. It is categorised as a Read tool in the Tradememory Protocol MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for evolution_get_log. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Tradememory Protocol MCP server.
evolution_get_log 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 evolution_get_log 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.
Set action: deny in the Intercept policy for evolution_get_log. 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.
evolution_get_log is provided by the Tradememory Protocol MCP server (mnemox-ai/tradememory-protocol). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept