Searches contacts/users with aliases, tags, and notes.
AI agents call contactsSearch to retrieve information from Telegram MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries contact information based on search criteria. It performs no write, destructive, execute, or financial operations—it is a pure read operation that returns existing contact data. The low severity reflects that searching contacts has minimal blast radius; misuse would at worst expose already-stored contact metadata, which is a confidentiality concern rather than an operational risk.
From the tool's definition Tool name is 'contactsSearch' and description states it 'Searches contacts/users with aliases, tags, and notes.' The verb 'searches' and the query-like nature indicate data retrieval without modification.
Documented attack patterns abuse exactly the kind of access contactsSearch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Telegram MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for contactsSearch:
{
"version": "1",
"default": "deny",
"tools": {
"contactsSearch": {}
}
}contactsSearch 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.
Searches contacts/users with aliases, tags, and notes. It is categorised as a Read tool in the Telegram MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Telegram MCP Server MCP server in PolicyLayer and add a rule for contactsSearch: 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 Telegram MCP Server. Nothing to install.
contactsSearch 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 contactsSearch 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 contactsSearch. 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.
contactsSearch is provided by the Telegram MCP Server MCP server (kfastov/tgcli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Telegram MCP Server, 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.
38 Telegram MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.