who_did_what
Convenience join answering
This record as markdown: /tools/danielsimonjr-memory-mcp/who-did-what.md
What who_did_what does on Enhanced Knowledge Graph Memory Server
AI agents call who_did_what 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 who_did_what is rated Low
This tool retrieves and correlates existing data from the knowledge graph to answer questions about entity relationships and actions. It performs no modifications, deletions, or external operations—it is purely a read operation that queries and joins stored information.
From the tool's definition Tool name 'who_did_what' and description 'Convenience join answering' indicate a query/retrieval function that joins data to answer analytical questions.
Attacks that exploit this kind of access
The rule that runs who_did_what 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 who_did_what, this is the rule to start with:
who_did_what 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 who_did_what call is checked against it from then on.
Questions about who_did_what
Convenience join answering. 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 who_did_what: 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.
who_did_what 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 who_did_what 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 who_did_what. 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.
who_did_what 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