Low Risk

telegram_get_messages

Read messages from a Telegram chat. Chat can be @username, phone, or numeric ID.

How to control telegram_get_messages ↓

What telegram_get_messages does on Odoo Claude MCP

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

Low Risk

Why telegram_get_messages needs a policy

This tool retrieves/queries data from Telegram (messages from a chat specified by username, phone, or ID) without creating, modifying, deleting, or executing operations. It is a straightforward read operation with minimal blast radius — an AI agent misuse would result in unauthorized data access but not destructive or financial harm.

From the tool's definition Tool description states 'Read messages from a Telegram chat' — the verb 'Read' and the action of retrieving messages with no modification capability clearly indicates data retrieval with no side effects.

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

How to control telegram_get_messages

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

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

telegram_get_messages 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 Odoo Claude MCP — 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 telegram_get_messages

What does the telegram_get_messages tool do? +

Read messages from a Telegram chat. Chat can be @username, phone, or numeric ID. 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_messages? +

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

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

Can I rate-limit telegram_get_messages? +

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

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

telegram_get_messages 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.

Enforce policy on every Odoo Claude MCP tool call.

Start from Odoo Claude MCP, 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.

180 Odoo Claude MCP 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.