Low Risk

discover_related_conversations

CROSS-PLATFORM DISCOVERY: Find related conversations across ALL AI platforms. Uses Purmemo's semantic clustering to automatically discover conversations about similar topics, regardless of which AI platform was used (ChatGPT, Claude Desktop, Gemini, etc). WHAT THIS DOES: - Searches for memories m...

Risk signalsAccepts freeform code/query input (query) · Bulk/mass operation — affects multiple targets

Part of the Pūrmemo server.

discover_related_conversations is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE PŪRMEMO →

Free to start. No card required.

AI agents call discover_related_conversations to retrieve information from Pūrmemo without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though discover_related_conversations only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "discover_related_conversations": {}
  }
}

See the full Pūrmemo policy for all 11 tools.

Get this rule live on your own Pūrmemo server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY PŪRMEMO →

View all 11 tools →

These attack patterns abuse exactly the kind of access discover_related_conversations gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so discover_related_conversations only ever does what you allow.

SECURE PŪRMEMO →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the discover_related_conversations tool do? +

CROSS-PLATFORM DISCOVERY: Find related conversations across ALL AI platforms. Uses Purmemo's semantic clustering to automatically discover conversations about similar topics, regardless of which AI platform was used (ChatGPT, Claude Desktop, Gemini, etc). WHAT THIS DOES: - Searches for memories matching your query - Uses AI-organized semantic clusters to find related conversations - Groups results by topic cluster with platform indicators - Shows conversations you may have forgotten about on other platforms EXAMPLES: User: "Show me all conversations about the marketing project" → Finds conversations across ChatGPT, Claude, Gemini automatically User: "What have I discussed about licensing requirements?" → Discovers related discussions from all platforms, grouped by semantic similarity User: "Find everything about React hooks" → Returns conversations from any platform where you discussed React hooks RESPONSE FORMAT: Shows memories grouped by semantic cluster with platform badges (ChatGPT, Claude, Gemini) Each cluster represents conversations about similar topics across all platforms. It is categorised as a Read tool in the Pūrmemo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on discover_related_conversations? +

Register the Pūrmemo MCP server in PolicyLayer and add a rule for discover_related_conversations: 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 Pūrmemo. Nothing to install.

What risk level is discover_related_conversations? +

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

Can I rate-limit discover_related_conversations? +

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

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

discover_related_conversations is provided by the Pūrmemo MCP server (purmemo/purmemo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pūrmemo tool call.

Deterministic rules across all 11 Pūrmemo tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.