restrict_participant · Claudegram MCP: Risk & Policy

WHAT IT DOES

What restrict_participant does on Claudegram

AI agents invoke restrict_participant 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.

WHY IT NEEDS A POLICY

Why restrict_participant needs a policy

Based on the tool name and server context, 'restrict_participant' almost certainly applies restrictions (e.g., mute, limit permissions) to a Telegram chat participant. This is an action with real external effects on another user's abilities in a chat, classifying it as Execute. Severity is high because misuse could silently restrict legitimate users in group chats. Confidence is reduced due to the empty description.

From the tool's definition Tool name 'restrict_participant' on a Telegram MTProto server with 120+ tools for chat management; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restrict_participant Rate-limited

restrict_participant stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "restrict_participant": {
      "limits": [
        {
          "counter": "restrict_participant_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about restrict_participant

What does the restrict_participant tool do? +

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

How do I enforce a policy on restrict_participant? +

Register the Claudegram MCP server in PolicyLayer and add a rule for restrict_participant: 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.

What risk level is restrict_participant? +

restrict_participant is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit restrict_participant? +

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

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

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