query_events

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/query-events.md

WHAT IT DOES

What query_events does on Enhanced Knowledge Graph Memory Server

AI agents call query_events 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.

RISK

Why query_events is rated Low

Queries and retrieves event data with no mutation, deletion, or side effects.

From the tool's definition Query recorded events by any combination of actor, target, action, flowKey, time range

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs query_events 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 query_events, this is the rule to start with:

query_events Allowed

query_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_events": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Enhanced Knowledge Graph Memory Server, apply this rule, and every query_events call is checked against it from then on.

FAQ

Questions about query_events

What does the query_events tool do? +

Query recorded events by any combination of actor, target, action, flowKey, and inclusive time range. Results are chronologically ordered (occurredAt, falling back to createdAt). Uses relation/type indexes \u2014 never a full-graph scan. 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 query_events? +

Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for query_events: 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 query_events? +

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

Can I rate-limit query_events? +

Yes. Add a rate_limit block to the query_events 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 query_events completely? +

Set action: deny in the PolicyLayer policy for query_events. 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 query_events? +

query_events 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.

KEEP EXPLORING

More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.

This server

All 241 Enhanced Knowledge Graph Memory Server tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →