Retrieves the complete conversation history for a specific chat. Returns the full chat history with all messages and their timestamps. No API calls are made to Perplexity - this only reads from local storage.
AI agents call read_chat_perplexity to retrieve information from Perplexity 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 retrieval operation from local storage without side effects, data modification, or external state changes. It qualifies as a Read operation. Severity is low because retrieving chat history has minimal blast radius—an agent cannot cause harm beyond accessing existing conversation data. Confidence is high due to clear documentation of read-only behavior.
From the tool's definition Tool description explicitly states it 'Retrieves the complete conversation history' and 'only reads from local storage' with 'No API calls' and no modification capability.
Attacks that exploit this kind of access
Retrieves the complete conversation history for a specific chat. Returns the full chat history with all messages and their timestamps. No API calls are made to Perplexity - this only reads from local storage. It is categorised as a Read tool in the Perplexity MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Perplexity MCP Server MCP server in PolicyLayer and add a rule for read_chat_perplexity: 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 Perplexity MCP Server. Nothing to install.
read_chat_perplexity 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 read_chat_perplexity 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 read_chat_perplexity. 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.
read_chat_perplexity is provided by the Perplexity MCP Server MCP server (sengokudaikon/mcp-perplexity). 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 →