Configure the webhook URL where the bot receives events (messages, callbacks)
AI agents use set_webhook to create or update resources in Solafon MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Solafon MCP environment.
The tool creates or modifies bot configuration (the webhook URL) rather than reading, executing arbitrary code, deleting data, or moving funds. It is a configuration write operation. Severity is medium because misconfiguration of webhooks could redirect bot events to an attacker-controlled server, potentially exposing messages and callbacks, but the operation itself is reversible (the webhook can be changed again).
From the tool's definition Tool name is 'set_webhook' and description states 'Configure the webhook URL where the bot receives events (messages, callbacks)'. This modifies configuration by setting/updating a webhook endpoint, which is a reversible write operation.
Attacks that exploit this kind of access
Configure the webhook URL where the bot receives events (messages, callbacks). It is categorised as a Write tool in the Solafon MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Solafon MCP server in PolicyLayer and add a rule for set_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 Solafon MCP. Nothing to install.
set_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 set_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 set_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.
set_webhook is provided by the Solafon MCP server (solafon/solafon-mcp). 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 →