AI agents call get_history to retrieve information from Tgmcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical messages from a chat without altering, destroying, or creating any data. It is a straightforward read operation that queries existing chat history. No side effects or irreversible actions are possible. The severity is low because exposure of this tool allows data exfiltration but does not enable destructive actions, code execution, or financial transactions.
From the tool's definition Tool name 'get_history' combined with description 'Get full chat history (up to limit)' indicates retrieval of existing data with no modification, creation, deletion, or execution of operations.
Attacks that exploit this kind of access
Get full chat history (up to limit). It is categorised as a Read tool in the Tgmcp MCP Server, which means it retrieves data without modifying state.
Register the Tg MCP server in PolicyLayer and add a rule for get_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 Tgmcp. Nothing to install.
get_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_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_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_history is provided by the Tg MCP server (oevortex/tgmcp). 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 →