Get the chat history for a given chat blob id until the limit is reached retrieve saved chat history. By default, this will retrieve history entries associated with your API key. If you provide a specific sdkUniqueId, it will retrieve history entries associated with that chat blob id. Args: sdkUn...
AI agents call chaingpt_get_chat_history to retrieve information from ChainGPT 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 data without any side effects or ability to modify, delete, or execute operations. It is a straightforward data retrieval function that queries existing chat history records associated with an API key or specific chat blob ID.
From the tool's definition Tool description states 'retrieve saved chat history' and 'Get the chat history for a given chat blob id until the limit is reached'. The parameters (sdkUniqueId, limit, offset, sortBy) are all consistent with a read/retrieval operation.
Attacks that exploit this kind of access
Get the chat history for a given chat blob id until the limit is reached retrieve saved chat history. By default, this will retrieve history entries associated with your API key. If you provide a specific sdkUniqueId, it will retrieve history entries associated with that chat blob id. Args: sdkUniqueId (str): The unique identifier for the chat. limit (int, optional): The maximum number of chat history items to return. Default is 10. offset (int, optional): The offset to start the chat history from. Default is 0. sortBy (str, optional): The field to sort the chat history by. Default is. It is categorised as a Read tool in the ChainGPT MCP MCP Server, which means it retrieves data without modifying state.
Register the ChainGPT MCP server in PolicyLayer and add a rule for chaingpt_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 ChainGPT MCP. Nothing to install.
chaingpt_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 chaingpt_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 chaingpt_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.
chaingpt_get_chat_history is provided by the ChainGPT MCP server (mikeysrecipes/chaingpt-mcp). 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 →