Query relations involving a specific entity URI.
AI agents call get_related_entities to retrieve information from Turbo Quant Memory MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves relationship data from a knowledge graph without creating, modifying, or deleting information. It is a read-only operation with minimal blast radius if misused by an AI agent (worst case: information disclosure of stored entity relationships).
From the tool's definition Tool description states 'Query relations involving a specific entity URI' — a pure query operation with no modification or side effects. The verb 'query' and the context of a knowledge graph indicate data retrieval only.
Documented attack patterns abuse exactly the kind of access get_related_entities gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Turbo Quant Memory MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_related_entities:
{
"version": "1",
"default": "deny",
"tools": {
"get_related_entities": {}
}
}get_related_entities is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Query relations involving a specific entity URI. It is categorised as a Read tool in the Turbo Quant Memory MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Turbo Quant Memory MCP Server MCP server in PolicyLayer and add a rule for get_related_entities: 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 Turbo Quant Memory MCP Server. Nothing to install.
get_related_entities 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_entities 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_entities. 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_entities is provided by the Turbo Quant Memory MCP Server MCP server (lexus2016/turbo_quant_memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Turbo Quant Memory MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
19 Turbo Quant Memory MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.