unblock_user

Unblock a user as the authenticated user

SERVERForgejo SOURCEsqcows/forgejo-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sqcows-forgejo-mcp/unblock-user.md

WHAT IT DOES

What unblock_user does on Forgejo

AI agents call unblock_user to retrieve information from Forgejo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why unblock_user is rated Low

Even though unblock_user only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs unblock_user safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Forgejo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unblock_user, this is the rule to start with:

unblock_user Allowed

unblock_user is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "unblock_user": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Forgejo, apply this rule, and every unblock_user call is checked against it from then on.

FAQ

Questions about unblock_user

What does the unblock_user tool do? +

Unblock a user as the authenticated user. It is categorised as a Read tool in the Forgejo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on unblock_user? +

Register the Forgejo 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 Forgejo. Nothing to install.

What risk level is unblock_user? +

unblock_user is a Read tool with low risk. Read-only tools are generally safe to allow by default.

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 Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Forgejo, and thousands of servers like it.

This server

All 457 Forgejo tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →