AI agents call telegram_auth_status 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.
This tool retrieves the current authentication state of a Telegram connection without modifying any data, creating side effects, or triggering external operations. It is a straightforward informational query, placing it firmly in the Read category with low severity due to minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'telegram_auth_status' and description states 'Check Telegram authentication status.' The verb 'check' and 'status' indicate a read-only query operation with no side effects or modifications.
Documented attack patterns abuse exactly the kind of access telegram_auth_status gives an agent:
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_auth_status:
{
"version": "1",
"default": "deny",
"tools": {
"telegram_auth_status": {}
}
} telegram_auth_status 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.
Check Telegram authentication status. It is categorised as a Read tool in the Odoo Claude MCP MCP Server, which means it retrieves data without modifying state.
Register the Odoo Claude MCP server in PolicyLayer and add a rule for telegram_auth_status: 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.
telegram_auth_status 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_auth_status 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_auth_status. 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_auth_status 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.
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.