create_webhook
AI agents use create_webhook to create or update resources in CATS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CATS MCP Server environment.
Webhook creation is a Write operation—it establishes a new data flow or integration point in the recruiting system that persists and affects future operations. However, it carries high severity because misconfigured webhooks could expose candidate/job data to unauthorized external endpoints, leak PII, or enable account compromise through callback manipulation.
From the tool's definition Tool name is 'create_webhook' which creates a new webhook resource. The description is empty, providing no additional context, but webhook creation is a write operation that modifies system state by adding a new integration endpoint.
Attacks that exploit this kind of access
create_webhook. It is categorised as a Write tool in the CATS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CATS MCP Server MCP server in PolicyLayer and add a rule for create_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 CATS MCP Server. Nothing to install.
create_webhook is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_webhook is provided by the CATS MCP Server MCP server (vanman2024/cats-mcp-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 →