Low Risk

telegram-get-my-role

Get the current user

How to control telegram-get-my-role ↓

What telegram-get-my-role does on MCP-Telegram

AI agents call telegram-get-my-role to retrieve information from MCP-Telegram without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why telegram-get-my-role needs a policy

This tool retrieves user identity information with no side effects. Although the MCP server itself operates as a userbot with broad access to Telegram account data, this specific tool is read-only. The low severity reflects that retrieving one's own user role carries minimal risk even if misused—it cannot alter data, execute actions, or cause financial harm.

From the tool's definition Tool name 'telegram-get-my-role' and description 'Get the current user' indicate a query operation that retrieves information about the authenticated user's role/identity without modifying any data.

Documented attack patterns abuse exactly the kind of access telegram-get-my-role gives an agent:

How to control telegram-get-my-role

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Telegram, and nothing reaches the server without passing your rules. This is the rule we recommend for telegram-get-my-role:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "telegram-get-my-role": {}
  }
}

telegram-get-my-role is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP-Telegram — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about telegram-get-my-role

What does the telegram-get-my-role tool do? +

Get the current user. It is categorised as a Read tool in the MCP-Telegram MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on telegram-get-my-role? +

Register the MCP-Telegram MCP server in PolicyLayer and add a rule for telegram-get-my-role: 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 MCP-Telegram. Nothing to install.

What risk level is telegram-get-my-role? +

telegram-get-my-role is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit telegram-get-my-role? +

Yes. Add a rate_limit block to the telegram-get-my-role 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-get-my-role completely? +

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

telegram-get-my-role is provided by the MCP-Telegram MCP server (mcp-telegram/mcp-telegram). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP-Telegram tool call.

Start from MCP-Telegram, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

181 MCP-Telegram tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.