AI agents call list_messages 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.
The tool retrieves or queries message data from Telegram without side effects. Although the description is empty and provides no explicit confirmation, the name 'list_messages' strongly indicates a non-destructive read operation.
From the tool's definition Tool name 'list_messages' indicates a retrieval operation with no modification capability. The 'list' verb is a standard query operation.
Attacks that exploit this kind of access
list_messages. 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 list_messages: 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.
list_messages 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 list_messages 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 list_messages. 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.
list_messages 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 →