update_repository_webhook_config

WHAT IT DOES

What update_repository_webhook_config does on Mcp Github

AI agents use update_repository_webhook_config to create or update resources in Mcp Github — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Github environment.

WHY IT NEEDS A POLICY

Why update_repository_webhook_config needs a policy

This tool modifies repository webhook settings reversibly (webhooks can be reconfigured or disabled). It is categorized as Write rather than Execute because it configures external integrations rather than directly executing code.

From the tool's definition Tool name 'update_repository_webhook_config' and description 'Update webhook config for a repository webhook' indicate modification of webhook configuration. Webhooks control external integrations and event triggers for a GitHub repository.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_repository_webhook_config Rate-limited

update_repository_webhook_config 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": {
    "update_repository_webhook_config": {
      "limits": [
        {
          "counter": "update_repository_webhook_config_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 Mcp Github, so you can run agents against it safely.

FAQ

Questions about update_repository_webhook_config

What does the update_repository_webhook_config tool do? +

Update webhook config for a repository webhook. It is categorised as a Write tool in the Mcp Github MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_repository_webhook_config? +

Register the Mcp Github MCP server in PolicyLayer and add a rule for update_repository_webhook_config: 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 Mcp Github. Nothing to install.

What risk level is update_repository_webhook_config? +

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

Can I rate-limit update_repository_webhook_config? +

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

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

update_repository_webhook_config is provided by the Mcp Github MCP server (@missionsquad/mcp-github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.