Page through historical memories in a space by memory_type.
AI agents call fetch_history to retrieve information from Evermemos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical data (memories) from storage with pagination/filtering capabilities. The action is read-only with no side effects. Severity is medium rather than low because the tool may expose sensitive context or coding information that could be useful to an attacker if the AI agent is compromised, but the tool itself has no destructive or operational impact.
From the tool's definition Tool 'fetch_history' is described as 'Page through historical memories in a space by memory_type' — it retrieves and queries stored memory records without modifying, deleting, or executing external operations.
Documented attack patterns abuse exactly the kind of access fetch_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Evermemos, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_history:
{
"version": "1",
"default": "deny",
"tools": {
"fetch_history": {}
}
}fetch_history 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.
Page through historical memories in a space by memory_type. It is categorised as a Read tool in the Evermemos MCP Server, which means it retrieves data without modifying state.
Register the Evermemos MCP server in PolicyLayer and add a rule for fetch_history: 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 Evermemos. Nothing to install.
fetch_history 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 fetch_history 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 fetch_history. 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.
fetch_history is provided by the Evermemos MCP server (tt-a1i/evermemos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Evermemos, 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.
7 Evermemos tools catalogued and risk-classified — across an index of 43,000+ MCP servers.