unblock_user · Tg MCP: Risk & Policy

WHAT IT DOES

What unblock_user does on Tgmcp

AI agents use unblock_user 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 unblock_user needs a policy

Unblocking a user reverses a block action, modifying the account's block list. This is a reversible write operation — the user can be blocked again. It has moderate blast radius as it could allow unwanted users to contact the account again, but it does not delete data or move money.

From the tool's definition Unblock a user by user ID

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

unblock_user Rate-limited

unblock_user 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": {
    "unblock_user": {
      "limits": [
        {
          "counter": "unblock_user_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 unblock_user

What does the unblock_user tool do? +

Unblock a user by user ID. 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 unblock_user? +

Register the Tg MCP server in PolicyLayer and add a rule for unblock_user: 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 unblock_user? +

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

Can I rate-limit unblock_user? +

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

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

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