telegram_agent_unenroll

THE RISK

Critical Risk

Why telegram_agent_unenroll needs a policy

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

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

POLICY

How to control telegram_agent_unenroll

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_agent_unenroll:

policy.json

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

telegram_agent_unenroll disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Odoo Claude MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Odoo Claude MCP tools

Destructive cf_dns_delete Delete a DNS record. Destructive cf_tunnel_route_remove Remove ingress rule by hostname + delete its CNAME record. Destructive ee_unlink Remove symlinks for EE modules from addons path. Destructive google_calendar_delete_event Delete a calendar event. Destructive memory_delete Delete a memory file from personal or shared storage. Destructive odoo_fp_remove_action Remove a tax action map entry from a fiscal position (l10n_bg_tax_admin). Destructive odoo_stock_initial_delete Delete wrong opening stock balances — cascade-removes stock.move (is_inventory=TRUE) Destructive odoo_stock_mo_delete_draft Safely DELETE a draft or cancelled mrp.production with cascade (raw stock.moves,

All 180 Odoo Claude MCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Odoo Claude MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

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.

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.

CHECK YOUR STACK →