AI agents call get-me to retrieve information from Telegram Bot 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 information about the bot itself (likely its ID, username, and basic metadata) without modifying any state or triggering external operations. It is a read-only diagnostic operation typical of API testing endpoints. No data is created, modified, deleted, or financial transactions are involved.
From the tool's definition Tool name 'get-me' and description 'A simple method for testing your bot' indicates retrieval of bot identity/status information with no side effects.
Documented attack patterns abuse exactly the kind of access get-me gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Telegram Bot MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-me:
{
"version": "1",
"default": "deny",
"tools": {
"get-me": {}
}
} get-me 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.
A simple method for testing your bot. It is categorised as a Read tool in the Telegram Bot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Telegram Bot MCP Server MCP server in PolicyLayer and add a rule for get-me: 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 Bot MCP Server. Nothing to install.
get-me 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-me 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-me. 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-me is provided by the Telegram Bot MCP Server MCP server (siavashdelkhosh81/telegram-bot-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Telegram Bot 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.
16 Telegram Bot MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.