telegram_agent_set_scenario

THE RISK

Medium Risk

Why telegram_agent_set_scenario needs a policy

This tool modifies an existing resource (the scenario associated with an enrolled chat) in a reversible manner. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely retrieve data (Read). The 'Replace' verb confirms write capability.

From the tool's definition Tool name 'telegram_agent_set_scenario' and description 'Replace the scenario for an enrolled chat' indicate modification of configuration/state for an existing Telegram chat integration.

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

POLICY

How to control telegram_agent_set_scenario

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "telegram_agent_set_scenario": {
      "limits": [
        {
          "counter": "telegram_agent_set_scenario_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

telegram_agent_set_scenario stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

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.

LIMIT 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 →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about telegram_agent_set_scenario

What does the telegram_agent_set_scenario tool do? +

Replace the scenario for an enrolled chat. It is categorised as a Write tool in the Odoo Claude MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on telegram_agent_set_scenario? +

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

telegram_agent_set_scenario is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit telegram_agent_set_scenario? +

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

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

telegram_agent_set_scenario 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 →