Return the full message history for a local chat session.
AI agents call get_chat_history to retrieve information from Grok MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical chat messages from a local session. It performs a pure read operation with no capability to modify, delete, or execute actions. The data returned is limited to a user's own chat history within a session, reducing blast radius. Severity is low because unauthorized access reveals conversation history but does not enable further compromise or destructive actions by itself.
From the tool's definition Tool name 'get_chat_history' and description 'Return the full message history for a local chat session' indicate retrieval of stored chat data without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_chat_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Grok MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_chat_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_chat_history": {}
}
}get_chat_history 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.
Return the full message history for a local chat session. It is categorised as a Read tool in the Grok MCP MCP Server, which means it retrieves data without modifying state.
Register the Grok MCP server in PolicyLayer and add a rule for get_chat_history: 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 Grok MCP. Nothing to install.
get_chat_history 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_chat_history 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_chat_history. 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_chat_history is provided by the Grok MCP server (merterbak/grok-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Grok MCP, 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.
22 Grok MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.