telegram_agent_list

List enrolled chats with their mode/persona/skills.

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-agent-list.md

WHAT IT DOES

What telegram_agent_list does on Odoo Claude MCP

AI agents call telegram_agent_list 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_agent_list is rated Low

This tool queries and retrieves information about enrolled Telegram chats, their modes, personas, and skills. It performs a read-only operation without creating, modifying, deleting, or executing any external operations. The blast radius is minimal as it only exposes metadata about chat configurations.

From the tool's definition Tool name contains 'list' and description states 'List enrolled chats' — a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs telegram_agent_list 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_agent_list, this is the rule to start with:

telegram_agent_list Allowed

telegram_agent_list 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_agent_list": {}
  }
}

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_agent_list call is checked against it from then on.

FAQ

Questions about telegram_agent_list

What does the telegram_agent_list tool do? +

List enrolled chats with their mode/persona/skills. 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_agent_list? +

Register the Odoo Claude MCP server in PolicyLayer and add a rule for telegram_agent_list: 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_agent_list? +

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

Can I rate-limit telegram_agent_list? +

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

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

telegram_agent_list 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

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →comfy_agent_compute on Comfy → The MCP Attack Database →

Guides

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