recall_conversation
Recall a vaguely remembered Discord conversation in one permitted guild. Searches one to five caller-supplied literal phrase variants through Discord
This record as markdown: /tools/app-lasers-guildcontrol-discord/recall-conversation.md
What recall_conversation does on GuildControl MCP
AI agents call recall_conversation to retrieve information from GuildControl MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why recall_conversation is rated Low
Searches through conversation history for matching phrases without side effects.
From the tool's definition Recall, searches, Discord conversation, no modification or deletion.
Attacks that exploit this kind of access
The rule that runs recall_conversation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GuildControl MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For recall_conversation, this is the rule to start with:
recall_conversation 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 GuildControl MCP, apply this rule, and every recall_conversation call is checked against it from then on.
Questions about recall_conversation
Recall a vaguely remembered Discord conversation in one permitted guild. Searches one to five caller-supplied literal phrase variants through Discord. It is categorised as a Read tool in the GuildControl MCP MCP Server, which means it retrieves data without modifying state.
Register the GuildControl MCP server in PolicyLayer and add a rule for recall_conversation: 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 GuildControl MCP. Nothing to install.
recall_conversation 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 recall_conversation 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 recall_conversation. 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.
recall_conversation is provided by the GuildControl MCP server (guildctl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GuildControl, and thousands of servers like it.
This server
Across the catalogue