episodic_search
Return past episodic events matching a keyword query.
This record as markdown: /tools/ashlesh-t-cognirepo/episodic-search.md
What episodic_search does on CogniRepo
AI agents call episodic_search to retrieve information from CogniRepo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why episodic_search is rated Low
This tool retrieves historical episodic memory data based on search criteria. It has no capability to modify, delete, execute code, or perform financial operations. The blast radius of misuse is minimal—an agent could retrieve irrelevant or sensitive historical context, but cannot alter system state or trigger external actions. This is a straightforward read/query operation.
From the tool's definition Tool performs 'Return past episodic events matching a keyword query' - a retrieval operation with no modification or execution capability. The verb 'Return' and the query-based nature indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs episodic_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CogniRepo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For episodic_search, this is the rule to start with:
episodic_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CogniRepo, apply this rule, and every episodic_search call is checked against it from then on.
Questions about episodic_search
Return past episodic events matching a keyword query. It is categorised as a Read tool in the CogniRepo MCP Server, which means it retrieves data without modifying state.
Register the CogniRepo MCP server in PolicyLayer and add a rule for episodic_search: 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 CogniRepo. Nothing to install.
episodic_search 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 episodic_search 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 episodic_search. 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.
episodic_search is provided by the CogniRepo MCP server (pypi:cognirepo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CogniRepo, and thousands of servers like it.
This server
Across the catalogue