Search for related conversations from other workspaces based on code entities (classes, files, methods). Use this to find relevant context when analyzing code.
AI agents call get_related_context to retrieve information from Context Persistence MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search/query operation across persisted conversations based on code entity matching. It retrieves and reads data from the SQLite persistence layer without creating, modifying, or deleting information. The 'smart entity matching' is a read-side filtering mechanism.
From the tool's definition Tool name 'get_related_context' and description explicitly states 'Search for related conversations' - a retrieval operation with no modification capability.
Attacks that exploit this kind of access
Search for related conversations from other workspaces based on code entities (classes, files, methods). Use this to find relevant context when analyzing code. It is categorised as a Read tool in the Context Persistence MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Context Persistence MCP Server MCP server in PolicyLayer and add a rule for get_related_context: 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 Context Persistence MCP Server. Nothing to install.
get_related_context 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 get_related_context 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 get_related_context. 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.
get_related_context is provided by the Context Persistence MCP Server MCP server (jayasimhag1reddy/context-persistance). 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 →