search_users

THE RISK

Low Risk

Why search_users needs a policy

This tool performs a search/query operation to retrieve user information from the Forgejo instance. It has no side effects, does not modify data, execute code, delete resources, or move money. The classification as Read is appropriate for a search function.

From the tool's definition Tool name 'search_users' and description 'Search for users on the Forgejo instance' indicate a query operation that retrieves user data without modification.

Documented attack patterns abuse exactly the kind of access search_users gives an agent:

POLICY

How to control search_users

PolicyLayer is an MCP gateway — it sits between your AI agents and Forgejo, and nothing reaches the server without passing your rules. This is the rule we recommend for search_users:

policy.json

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

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

Create a free account and register Forgejo — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Forgejo tools

Destructive admin_delete_user Delete a user (requires admin privileges) Destructive delete_branch Delete a branch from a repository Destructive delete_file Delete a file from a repository Destructive delete_issue_comment Delete a comment on an issue Destructive delete_label Delete a label from a repository Destructive delete_milestone Delete a milestone from a repository Destructive delete_org Delete an organization Destructive delete_repo Delete a repository by owner and name

All 103 Forgejo tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about search_users

What does the search_users tool do? +

Search for users on the Forgejo instance. 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 search_users? +

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

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

Can I rate-limit search_users? +

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

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

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

Enforce policy on every Forgejo tool call.

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

CHECK YOUR STACK →