audit_query

Query the audit log for operations matching filter criteria (operation type, agent ID, entity name, date range)

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

WHAT IT DOES

What audit_query does on Enhanced Knowledge Graph Memory Server

AI agents call audit_query 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 audit_query is rated Low

This tool only retrieves historical audit data based on specified filters. It has no side effects, does not modify or delete data, and does not execute operations. It is a pure read operation that queries an immutable audit log, making it low severity with appropriate confidence.

From the tool's definition Tool description explicitly states it 'Query[s] the audit log' with filter criteria (operation type, agent ID, entity name, date range). No modification, deletion, or execution capabilities mentioned.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

audit_query Allowed

audit_query 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": {
    "audit_query": {}
  }
}

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 audit_query call is checked against it from then on.

FAQ

Questions about audit_query

What does the audit_query tool do? +

Query the audit log for operations matching filter criteria (operation type, agent ID, entity name, date range). 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 audit_query? +

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

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

Can I rate-limit audit_query? +

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

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

audit_query 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 225 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 →