Шаг 2: отправить код (и опц. пароль 2FA).
AI agents invoke auth_submit_code to trigger actions in Claudegram. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool submits an authentication code (and optionally a 2FA password) to log into a personal Telegram account. Completing account authentication grants full access to all 120+ tools on this server, including messaging, media, chat management, and more. Misuse could result in unauthorized account takeover or enable a cascade of destructive/privacy-violating actions across the entire Telegram account.
From the tool's definition 'auth_submit_code' - Step 2: submit code (and optional 2FA password). This completes authentication to a Telegram account via MTProto.
Attacks that exploit this kind of access
Шаг 2: отправить код (и опц. пароль 2FA). It is categorised as a Execute tool in the Claudegram MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claudegram MCP server in PolicyLayer and add a rule for auth_submit_code: 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 Claudegram. Nothing to install.
auth_submit_code is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the auth_submit_code 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 auth_submit_code. 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.
auth_submit_code is provided by the Claudegram MCP server (sanjar-x/claudegram). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →