get_expired_entities

Return all entities that have passed their TTL expiry

SERVEREnhanced Knowledge Graph Memory Server SOURCEdanielsimonjr/memory-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about get_expired_entities

What does the get_expired_entities tool do? +

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.

How do I enforce a policy on get_expired_entities? +

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.

What risk level is get_expired_entities? +

get_expired_entities is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_expired_entities? +

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.

How do I block get_expired_entities completely? +

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.

What MCP server provides get_expired_entities? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Enhanced Knowledge Graph Memory Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.