Get webhook config for an organization webhook
AI agents call get_organization_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.
This tool retrieves/queries webhook configuration data from GitHub without creating, modifying, deleting, or executing any operations. It is a pure read operation with no side effects. Severity is low because exposure of webhook configuration details has limited blast radius—webhook URLs and settings are typically known to organization members and the configuration itself does not directly execute actions.
From the tool's definition Tool name 'get_organization_webhook_config' and description 'Get webhook config for an organization webhook' both indicate retrieval of webhook configuration without modification.
Attacks that exploit this kind of access
Get webhook config for an organization webhook. It is categorised as a Read tool in the Mcp Github MCP Server, which means it retrieves data without modifying state.
Register the Mcp Github MCP server in PolicyLayer and add a rule for get_organization_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.
get_organization_webhook_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_organization_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.
Set action: deny in the PolicyLayer policy for get_organization_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.
get_organization_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.
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 →