search_by_date_range
Search entities within a date range, with optional filtering by entity type and tags. At least one of startDate or endDate should be provided.
This record as markdown: /tools/danielsimonjr-memory-mcp/search-by-date-range.md
What search_by_date_range does on Enhanced Knowledge Graph Memory Server
AI agents call search_by_date_range 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_date_range is rated Low
This tool retrieves or queries data from the knowledge graph based on date range and optional filters (entity type, tags). It has no side effects, does not modify state, and matches the Read category definition of 'retrieves or queries data; no side effects.' The severity is low because even if an AI agent misuses this for overly broad searches, the blast radius is limited to information disclosure with no…
From the tool's definition Tool description specifies 'Search entities within a date range' with optional filtering parameters. The operation is a query/retrieval function with no modification, creation, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs search_by_date_range 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_date_range, this is the rule to start with:
search_by_date_range 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_date_range call is checked against it from then on.
Questions about search_by_date_range
Search entities within a date range, with optional filtering by entity type and tags. At least one of startDate or endDate should be provided. 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_date_range: 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_date_range 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_date_range 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_date_range. 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_date_range 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