test_repo_hook

Send a test push event to a repository webhook

SERVERForgejo SOURCEsqcows/forgejo-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sqcows-forgejo-mcp/test-repo-hook.md

WHAT IT DOES

What test_repo_hook does on Forgejo

AI agents invoke test_repo_hook to trigger actions in Forgejo. 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.

RISK

Why test_repo_hook is rated High

Triggers an external webhook call, executing a push event to external systems.

From the tool's definition Send a test push event to a repository webhook

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs test_repo_hook 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 test_repo_hook, this is the rule to start with:

test_repo_hook Rate-limited

test_repo_hook 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": {
    "test_repo_hook": {
      "limits": [
        {
          "counter": "test_repo_hook_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about test_repo_hook

What does the test_repo_hook tool do? +

Send a test push event to a repository webhook. It is categorised as a Execute tool in the Forgejo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_repo_hook? +

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

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

Can I rate-limit test_repo_hook? +

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

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

test_repo_hook 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 → High-risk tools on this server →

Across the catalogue

execute_test_case on Percepta MCP Server →hook_function on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →