webhook_scaffold_handler · LaunchFrame MCP: Risk & Policy

WHAT IT DOES

What webhook_scaffold_handler does on LaunchFrame MCP

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

WHY IT NEEDS A POLICY

Why webhook_scaffold_handler needs a policy

This tool generates and likely writes scaffold code (controller and Bull processor files) for a new webhook handler. Creating new files/code artifacts is a Write operation. It does not execute code, delete data, or involve financial transactions. Severity is medium because scaffolded code could introduce security issues if not reviewed, but the blast radius is limited to code generation.

From the tool's definition 'Get a scaffold for a new webhook handler: controller receipt + Bull processor for a given provider and event type'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

webhook_scaffold_handler Rate-limited

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches LaunchFrame MCP, so you can run agents against it safely.

FAQ

Questions about webhook_scaffold_handler

What does the webhook_scaffold_handler tool do? +

Get a scaffold for a new webhook handler: controller receipt + Bull processor for a given provider and event type. It is categorised as a Write tool in the LaunchFrame MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on webhook_scaffold_handler? +

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

What risk level is webhook_scaffold_handler? +

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

Can I rate-limit webhook_scaffold_handler? +

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

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

webhook_scaffold_handler is provided by the LaunchFrame MCP server (launchframe-dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.