get_repository_webhook_config

Get webhook config for a repository webhook

Server Mcp Github @missionsquad/mcp-github
Category Read
Risk class Low
Parameters 00 required

What get_repository_webhook_config does on Mcp Github

AI agents call get_repository_webhook_config to retrieve information from Mcp Github without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_repository_webhook_config needs a policy

This tool queries and retrieves webhook configuration information from a GitHub repository. It performs no mutations, deletions, or side effects—it only reads and returns existing data. The blast radius of misuse is minimal; an attacker would only gain visibility into webhook endpoints and settings already configured on the repository, which does not enable unauthorized actions beyond information disclosure.

From the tool's definition Tool name 'get_repository_webhook_config' with description 'Get webhook config for a repository webhook' indicates a retrieval operation. The 'get_' prefix and verb 'Get' confirm it retrieves existing webhook configuration data without modification.

Questions about get_repository_webhook_config

What does the get_repository_webhook_config tool do? +

Get webhook config for a repository webhook. It is categorised as a Read tool in the Mcp Github MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_repository_webhook_config? +

Register the Mcp Github MCP server in PolicyLayer and add a rule for get_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 get_repository_webhook_config? +

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

Can I rate-limit get_repository_webhook_config? +

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

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

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.