webhooks_manage

SERVERGapup Mcp SOURCEhttps://mcp.gapup.io/mcp

Medium RISK CLASS

Category Write

Parameters 71 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-getgapup-gapup-mcp/webhooks-manage.md

WHAT IT DOES

What webhooks_manage does on Gapup Mcp

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

Parameter	Type	Required	Description
`url`	string	—	(register) HTTPS/HTTP endpoint that will receive POST callbacks. Must return 2xx within 10s.
`mode`	string	Yes	register — add a webhook endpoint. list — view your active webhooks. revoke — soft-delete a webhook by webhook_id. test — fire a test payload to verify the rece
`async`	boolean	—	If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti
`events`	array	—	(register, optional) Events to subscribe to. Defaults to all events if omitted.
`secret`	string	—	(register, optional) A secret string used to sign deliveries with HMAC-SHA256. Store it safely — verify X-Gapup-Signature header on your receiver.
`webhook_id`	string	—	(revoke / test / history) The webhook_id returned from register.
`caller_hash`	string	—	Optional caller identity override. If omitted, uses the internal session hash.

Parameters from the server's own tool schema.

RISK

Why webhooks_manage is rated Medium

This tool's primary function is to create and modify webhook endpoint registrations ('register', 'revoke' soft-delete, 'test'). While it does not permanently destroy data (revoke is soft-delete) and does not execute arbitrary code directly, it creates and modifies persistent callback configurations that determine what external systems receive sensitive async job results.

From the tool's definition The tool enables 'register (add endpoint)', 'revoke (soft-delete)', and 'test (fire a test payload)' operations that create, modify, and trigger webhook configurations.

Risk signalsAccepts URL/endpoint input (url) · Handles credentials or secrets (secret) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs webhooks_manage safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gapup Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For webhooks_manage, this is the rule to start with:

webhooks_manage Rate-limited

webhooks_manage 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": {
    "webhooks_manage": {
      "limits": [
        {
          "counter": "webhooks_manage_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gapup Mcp, apply this rule, and every webhooks_manage call is checked against it from then on.

FAQ

Questions about webhooks_manage

What does the webhooks_manage tool do? +

Manage HTTP webhook callbacks for async tools (T5/T6 batch flagships). Instead of polling every 5s, register a callback URL — Gapup posts the job result to your endpoint the moment it completes. Supported events: job.completed | job.failed | monitoring.alert | quota.threshold. Modes: register (add endpoint), list (view active webhooks), revoke (soft-delete), test (fire a test payload to verify your receiver), history (last 20 fires). Security: every delivery is signed with HMAC-SHA256 on the body — verify the X-Gapup-Signature header against sha256(secret, body). It is categorised as a Write tool in the Gapup Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does webhooks_manage accept? +

webhooks_manage accepts 7 parameters: url, mode, async, events, secret, webhook_id, caller_hash. Required: mode. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on webhooks_manage? +

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

What risk level is webhooks_manage? +

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

Can I rate-limit webhooks_manage? +

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

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

webhooks_manage is provided by the Gapup MCP server (https://mcp.gapup.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gapup, and thousands of servers like it.

This server

All 271 Gapup tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →