AI agents call telegram_get_bot_info to retrieve information from autoMate without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about a Telegram bot (likely name, description, commands, etc.) without modifying any data, triggering actions, or causing side effects. It is a pure information retrieval operation, clearly fitting the Read category. The severity is low because accessing public bot metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name is 'telegram_get_bot_info' and description states 'Get basic info about the Telegram bot.' The verb 'Get' and phrase 'basic info' indicate a read-only query operation with no side effects.
Documented attack patterns abuse exactly the kind of access telegram_get_bot_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and autoMate, and nothing reaches the server without passing your rules. This is the rule we recommend for telegram_get_bot_info:
{
"version": "1",
"default": "deny",
"tools": {
"telegram_get_bot_info": {}
}
}telegram_get_bot_info 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.
Get basic info about the Telegram bot. It is categorised as a Read tool in the autoMate MCP Server, which means it retrieves data without modifying state.
Register the autoMate MCP server in PolicyLayer and add a rule for telegram_get_bot_info: 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 autoMate. Nothing to install.
telegram_get_bot_info 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 telegram_get_bot_info 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 telegram_get_bot_info. 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.
telegram_get_bot_info is provided by the autoMate MCP server (yuruotong1/automate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 128 autoMate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
128 autoMate tools catalogued and risk-classified — across an index of 42,500+ MCP servers.