Get memos created within a date range.
AI agents call get_memos_by_date_range to retrieve information from Memos MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves memos based on date criteria. It performs a read-only operation that retrieves existing data without side effects, modification, or irreversible actions. The blast radius of misuse is minimal—an agent could retrieve memos it shouldn't see, but cannot alter or delete them. This aligns with the 'Read' category definition: 'retrieves or queries data; no side effects'.
From the tool's definition Tool name 'get_memos_by_date_range' and description 'Get memos created within a date range' indicate a retrieval operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Get memos created within a date range. It is categorised as a Read tool in the Memos MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Memos MCP Server MCP server in PolicyLayer and add a rule for get_memos_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 Memos MCP Server. Nothing to install.
get_memos_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 get_memos_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 get_memos_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.
get_memos_by_date_range is provided by the Memos MCP Server MCP server (shaorou459/memos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →