get_conversation
Zwraca pełny transkrypt rozmowy po conversation_id.
This record as markdown: /tools/mapi-agent-memory/get-conversation.md
What get_conversation does on Mapi Agent Memory
AI agents call get_conversation to retrieve information from Mapi Agent Memory without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_conversation is rated Low
This is a Read operation that retrieves existing conversation history. Severity is medium rather than low because transcripts may contain sensitive personal information, authentication details, or proprietary business logic that could be exploited if an agent queries unauthorized conversations.
From the tool's definition get_conversation returns a conversation transcript (transkrypt rozmowy), a retrieval action that queries data by conversation_id without modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_conversation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mapi Agent Memory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_conversation, this is the rule to start with:
get_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 Mapi Agent Memory, apply this rule, and every get_conversation call is checked against it from then on.
Questions about get_conversation
Zwraca pełny transkrypt rozmowy po conversation_id. It is categorised as a Read tool in the Mapi Agent Memory MCP Server, which means it retrieves data without modifying state.
Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for get_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 Mapi Agent Memory. Nothing to install.
get_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 get_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 get_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.
get_conversation is provided by the Mapi Agent Memory MCP server (cabo0m/mapi-agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mapi Agent Memory, and thousands of servers like it.
This server
Across the catalogue