Create a new webhook for a project
AI agents use smartling_create_webhook to create or update resources in Smartling MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Smartling MCP Server environment.
Creating a webhook is a write operation that adds a new integration point to a project configuration. It modifies project state reversibly—webhooks can be deleted or disabled. While it enables external callbacks that could trigger side effects, the tool itself only creates the webhook configuration, not the actions it may trigger.
From the tool's definition Tool name includes 'create' and description states 'Create a new webhook for a project', indicating creation of a new configuration resource.
Attacks that exploit this kind of access
Create a new webhook for a project. It is categorised as a Write tool in the Smartling MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Smartling MCP Server MCP server in PolicyLayer and add a rule for smartling_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 Smartling MCP Server. Nothing to install.
smartling_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 smartling_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 smartling_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.
smartling_create_webhook is provided by the Smartling MCP Server MCP server (jacobolevy/smartling-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 →