Obtiene detalles de un webhook específico
AI agents call get_webhook 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 webhook configuration details from a GitHub repository. It performs a read-only query operation with no side effects—it does not create, modify, delete, or trigger any webhook. The worst case misuse would be information disclosure of webhook URLs or secrets if they are exposed in the response, which is a read-category risk. No code execution, financial impact, or data destruction occurs.
From the tool's definition Tool name 'get_webhook' and description 'Obtiene detalles de un webhook específico' (Gets details of a specific webhook) indicate retrieval of webhook configuration data without modification or execution.
Attacks that exploit this kind of access
Obtiene detalles de un webhook específico. 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_webhook: 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_webhook 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_webhook 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_webhook. 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_webhook is provided by the Mcp Github MCP server (pblarismendi/mcp-github-server). 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 →