set_bot_commands · Tg MCP: Risk & Policy

WHAT IT DOES

What set_bot_commands does on Tgmcp

AI agents use set_bot_commands to create or update resources in Tgmcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tgmcp environment.

WHY IT NEEDS A POLICY

Why set_bot_commands needs a policy

Setting bot commands modifies bot behavior and configuration reversibly, making it a Write operation. Severity is medium because misconfigured commands could disrupt bot functionality or enable unintended capabilities, but the changes are reversible. The empty description and reliance on the name and server context reduce confidence to 0.75.

From the tool's definition Tool name 'set_bot_commands' indicates modification of bot command configuration. Server description mentions 'admin functions,' which aligns with configuration management. The empty description prevents higher confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_bot_commands Rate-limited

set_bot_commands 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.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tgmcp, so you can run agents against it safely.

FAQ

Questions about set_bot_commands

What does the set_bot_commands tool do? +

set_bot_commands. It is categorised as a Write tool in the Tgmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_bot_commands? +

Register the Tg MCP server in PolicyLayer and add a rule for set_bot_commands: 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 Tgmcp. Nothing to install.

What risk level is set_bot_commands? +

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

Can I rate-limit set_bot_commands? +

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

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

set_bot_commands is provided by the Tg MCP server (oevortex/tgmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.