AI agents call get_direct_chat_by_contact 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 performs a lookup operation to locate and return information about an existing direct chat. It has no side effects; it does not create, modify, delete, or execute actions. It is purely informational, making it a Read category tool with low severity since exposure poses minimal risk — an agent can only discover existing chats the account has access to, without altering state or triggering external operations.
From the tool's definition Tool name and description indicate retrieval operation: 'Find a direct chat with a specific contact' — this is a query/search function that retrieves existing chat data without modification.
Attacks that exploit this kind of access
Find a direct chat with a specific contact by name, username, or phone. 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_direct_chat_by_contact: 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_direct_chat_by_contact 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_direct_chat_by_contact 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_direct_chat_by_contact. 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_direct_chat_by_contact 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 →