telegram_agent_set_scenario
Replace the scenario for an enrolled chat.
This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/telegram-agent-set-scenario.md
What telegram_agent_set_scenario does on Odoo Claude MCP
AI agents use telegram_agent_set_scenario to create or update resources in Odoo Claude MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Odoo Claude MCP environment.
Why telegram_agent_set_scenario is rated Medium
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.
Attacks that exploit this kind of access
The rule that runs telegram_agent_set_scenario 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_set_scenario, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every telegram_agent_set_scenario call is checked against it from then on.
Questions about telegram_agent_set_scenario
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.
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.
telegram_agent_set_scenario is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on Odoo Claude, and thousands of servers like it.
This server
Across the catalogue