happ_integration_webhook_events
Входящие вебхук-запросы интеграции за последние 7 дней: статус, HTTP-код, длительность, IP, ошибка валидации. Тело обрезано до 16 КБ, секреты скрыты. (GET /integrations/:id/webhook-events)
This record as markdown: /tools/happ-ai-platform-mcp/happ-integration-webhook-events.md
What happ_integration_webhook_events does on Platform
AI agents call happ_integration_webhook_events to retrieve information from Platform without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
skip | integer | — | |
take | integer | — | |
integrationId | string | Yes | companyIntegrationId |
Parameters from the server's own tool schema.
Why happ_integration_webhook_events is rated Low
Even though happ_integration_webhook_events only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs happ_integration_webhook_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Platform, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For happ_integration_webhook_events, this is the rule to start with:
happ_integration_webhook_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Platform, apply this rule, and every happ_integration_webhook_events call is checked against it from then on.
Questions about happ_integration_webhook_events
Входящие вебхук-запросы интеграции за последние 7 дней: статус, HTTP-код, длительность, IP, ошибка валидации. Тело обрезано до 16 КБ, секреты скрыты. (GET /integrations/:id/webhook-events). It is categorised as a Read tool in the Platform MCP Server, which means it retrieves data without modifying state.
happ_integration_webhook_events accepts 3 parameters: skip, take, integrationId. Required: integrationId. The full parameter table on this page comes from the server's own tool schema.
Register the Platform MCP server in PolicyLayer and add a rule for happ_integration_webhook_events: 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 Platform. Nothing to install.
happ_integration_webhook_events 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 happ_integration_webhook_events 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 happ_integration_webhook_events. 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.
happ_integration_webhook_events is provided by the Platform MCP server (@happ-ai/platform-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Platform, and thousands of servers like it.
This server
Across the catalogue