Medium Risk

webhooks_add

Create a new webhook

Part of the Ghost CMS MCP Server server.

webhooks_add can modify Ghost CMS MCP Server data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE GHOST CMS MCP SERVER →

Free to start. No card required.

AI agents use webhooks_add to create or modify resources in Ghost CMS MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call webhooks_add repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Ghost CMS MCP Server.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "webhooks_add": {
      "limits": [
        {
          "counter": "webhooks_add_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Ghost CMS MCP Server policy for all 44 tools.

Get this rule live on your own Ghost CMS MCP Server server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY GHOST CMS MCP SERVER →

View all 44 tools →

These attack patterns abuse exactly the kind of access webhooks_add gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so webhooks_add only ever does what you allow.

SECURE GHOST CMS MCP SERVER →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the webhooks_add tool do? +

Create a new webhook. It is categorised as a Write tool in the Ghost CMS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on webhooks_add? +

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

What risk level is webhooks_add? +

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

Can I rate-limit webhooks_add? +

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

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

webhooks_add is provided by the Ghost CMS MCP Server MCP server (hithereiamaliff/mcp-ghostcms). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ghost CMS MCP Server tool call.

Deterministic rules across all 44 Ghost CMS MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.