telegram_agent_unenroll

Stop agentic handling for a chat.

SERVEROdoo Claude MCP SOURCErosenvladimirov/odoo-claude-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/telegram-agent-unenroll.md

WHAT IT DOES

What telegram_agent_unenroll does on Odoo Claude MCP

AI agents call telegram_agent_unenroll to permanently remove resources in Odoo Claude MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why telegram_agent_unenroll is rated Critical

Unenrolling a chat from agentic handling removes a configuration or subscription-like state. While not deleting data outright, 'unenroll' typically represents an irreversible action that cannot be simply undone without re-enrolling, making it closer to Destructive than Write. The blast radius is medium as it affects a single chat's agentic capabilities.

From the tool's definition Stop agentic handling for a chat — 'unenroll' implies an irreversible removal of the agent enrollment for a chat

Attacks that exploit this kind of access

RECOMMENDED RULE

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

telegram_agent_unenroll Hidden

telegram_agent_unenroll is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "telegram_agent_unenroll"
  ]
}

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

FAQ

Questions about telegram_agent_unenroll

What does the telegram_agent_unenroll tool do? +

Stop agentic handling for a chat. It is categorised as a Destructive tool in the Odoo Claude MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on telegram_agent_unenroll? +

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

telegram_agent_unenroll is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit telegram_agent_unenroll? +

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

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

telegram_agent_unenroll 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 → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →