AI agents call recent to retrieve information from Memory-Plus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'recent' strongly implies retrieval of recent items, consistent with the sibling tool 'get_recent_memories'. The description is empty, so confidence is reduced, but in context of a RAG memory store, 'recent' most plausibly queries/lists recent memories without side effects. Classified as Read with low severity since it only retrieves local memory data.
From the tool's definition Tool name is 'recent'; sibling tools include 'get_recent_memories', suggesting this retrieves recently stored memories
Documented attack patterns abuse exactly the kind of access recent gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memory-Plus, and nothing reaches the server without passing your rules. This is the rule we recommend for recent:
{
"version": "1",
"default": "deny",
"tools": {
"recent": {}
}
}recent 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.
recent. It is categorised as a Read tool in the Memory-Plus MCP Server, which means it retrieves data without modifying state.
Register the Memory-Plus MCP server in PolicyLayer and add a rule for recent: 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 Memory-Plus. Nothing to install.
recent 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 recent 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 recent. 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.
recent is provided by the Memory-Plus MCP server (yuchen20/memory-plus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Memory-Plus tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Memory-Plus tools catalogued and risk-classified — across an index of 42,500+ MCP servers.