Low Risk

search_by_sender

按发送者搜索消息

How to control search_by_sender ↓

What search_by_sender does on Telegram MCP Complete

AI agents call search_by_sender to retrieve information from Telegram MCP Complete without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search_by_sender needs a policy

This tool searches and retrieves messages filtered by sender, which is a read-only operation with no side effects. It queries existing data without creating, modifying, deleting, or executing external operations. The low severity reflects minimal risk—an AI agent querying messages by sender cannot cause irreversible damage or financial harm.

From the tool's definition Tool name 'search_by_sender' and description '按发送者搜索消息' (search messages by sender) indicate a query/search operation that retrieves data without modifying or deleting it.

Documented attack patterns abuse exactly the kind of access search_by_sender gives an agent:

How to control search_by_sender

PolicyLayer is an MCP gateway — it sits between your AI agents and Telegram MCP Complete, and nothing reaches the server without passing your rules. This is the rule we recommend for search_by_sender:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_by_sender": {}
  }
}

search_by_sender is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Telegram MCP Complete — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_by_sender

What does the search_by_sender tool do? +

按发送者搜索消息. It is categorised as a Read tool in the Telegram MCP Complete MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_by_sender? +

Register the Telegram MCP Complete MCP server in PolicyLayer and add a rule for search_by_sender: 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 Complete. Nothing to install.

What risk level is search_by_sender? +

search_by_sender is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_by_sender? +

Yes. Add a rate_limit block to the search_by_sender 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.

How do I block search_by_sender completely? +

Set action: deny in the PolicyLayer policy for search_by_sender. 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.

What MCP server provides search_by_sender? +

search_by_sender is provided by the Telegram MCP Complete MCP server (you922/telegram-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Telegram MCP Complete tool call.

Start from Telegram MCP Complete, 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.

153 Telegram MCP Complete tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.