telegram_get_dialogs

List recent Telegram chats (users, groups, channels).

SERVEROdoo Claude MCP SOURCErosenvladimirov/odoo-claude-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/telegram-get-dialogs.md

WHAT IT DOES

What telegram_get_dialogs does on Odoo Claude MCP

AI agents call telegram_get_dialogs to retrieve information from Odoo Claude MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why telegram_get_dialogs is rated Low

The tool performs a read-only operation that enumerates Telegram conversations. It does not create, modify, delete, execute code, or trigger financial transactions. The primary risk is information disclosure (learning what chats exist), which is relatively low severity since it reveals metadata an authenticated user would typically see anyway in their own Telegram client.

From the tool's definition Tool name and description: 'List recent Telegram chats (users, groups, channels)' — retrieves or queries existing data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs telegram_get_dialogs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Odoo Claude MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For telegram_get_dialogs, this is the rule to start with:

telegram_get_dialogs Allowed

telegram_get_dialogs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "telegram_get_dialogs": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every telegram_get_dialogs call is checked against it from then on.

FAQ

Questions about telegram_get_dialogs

What does the telegram_get_dialogs tool do? +

List recent Telegram chats (users, groups, channels). It is categorised as a Read tool in the Odoo Claude MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on telegram_get_dialogs? +

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

What risk level is telegram_get_dialogs? +

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

Can I rate-limit telegram_get_dialogs? +

Yes. Add a rate_limit block to the telegram_get_dialogs 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 telegram_get_dialogs completely? +

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

telegram_get_dialogs is provided by the Odoo Claude MCP server (rosenvladimirov/odoo-claude-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Odoo Claude, and thousands of servers like it.

This server

All 246 Odoo Claude tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →