AI agents call memory_reflect to retrieve information from Jt without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs analysis/inspection of the knowledge graph without modifying or deleting any data. It is a read-only diagnostic operation that surfaces insights about the graph's state.
From the tool's definition Analyze the knowledge graph for health, staleness, contradictions, clusters, or tool usage
Attacks that exploit this kind of access
Analyze the knowledge graph for health, staleness, contradictions, clusters, or tool usage. It is categorised as a Read tool in the Jt MCP Server, which means it retrieves data without modifying state.
Register the Jt MCP server in PolicyLayer and add a rule for memory_reflect: 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 Jt. Nothing to install.
memory_reflect 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 memory_reflect 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 memory_reflect. 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.
memory_reflect is provided by the Jt MCP server (@houkasaurusrex/jt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →