get_expired_entities
Return all entities that have passed their TTL expiry
This record as markdown: /tools/danielsimonjr-memory-mcp/get-expired-entities.md
What get_expired_entities does on Enhanced Knowledge Graph Memory Server
AI agents call get_expired_entities 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 get_expired_entities is rated Low
This tool queries and retrieves a filtered list of entities based on their TTL expiration status. It performs no deletion, modification, execution, or financial transaction. The operation is read-only and has minimal blast radius—an agent misusing it could only retrieve data about expired entities, with no destructive consequences.
From the tool's definition Tool name 'get_expired_entities' combined with description 'Return all entities that have passed their TTL expiry' indicates a pure retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_expired_entities 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 get_expired_entities, this is the rule to start with:
get_expired_entities 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 get_expired_entities call is checked against it from then on.
Questions about get_expired_entities
Return all entities that have passed their TTL expiry. 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 get_expired_entities: 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.
get_expired_entities 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_expired_entities 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_expired_entities. 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_expired_entities 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