search_by_time
Search entities using a natural language time expression (e.g.
This record as markdown: /tools/danielsimonjr-memory-mcp/search-by-time.md
What search_by_time does on Enhanced Knowledge Graph Memory Server
AI agents call search_by_time to retrieve information from Enhanced Knowledge Graph Memory Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_by_time is rated Low
This tool retrieves or queries data from the knowledge graph without modifying, deleting, or executing external operations. Search and retrieval operations are Read category with low severity since they have no side effects and minimal blast radius if misused—an agent can only over-retrieve information it likely has authorization to access already.
From the tool's definition Tool name is 'search_by_time' and performs search/query operations on entities using natural language time expressions. The server description indicates this is a knowledge graph storage system where this tool retrieves data based on temporal criteria.
Attacks that exploit this kind of access
The rule that runs search_by_time safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_by_time, this is the rule to start with:
search_by_time 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 Enhanced Knowledge Graph Memory Server, apply this rule, and every search_by_time call is checked against it from then on.
Questions about search_by_time
Search entities using a natural language time expression (e.g. It is categorised as a Read tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for search_by_time: 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 Enhanced Knowledge Graph Memory Server. Nothing to install.
search_by_time 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 search_by_time 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 search_by_time. 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.
search_by_time is provided by the Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.
Across the catalogue