AI agents call get_webhooks to retrieve information from Iterable MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves webhook configuration data from the Iterable platform. The verb 'Get' and lack of any modification language clearly indicate a read-only operation. While webhooks could theoretically be used to exfiltrate data if misconfigured, the tool itself only retrieves existing webhook metadata without executing, modifying, or deleting anything.
From the tool's definition Tool name 'get_webhooks' and description 'Get all webhooks for the project' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_webhooks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Iterable MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_webhooks:
{
"version": "1",
"default": "deny",
"tools": {
"get_webhooks": {}
}
}get_webhooks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all webhooks for the project. It is categorised as a Read tool in the Iterable MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Iterable MCP Server MCP server in PolicyLayer and add a rule for get_webhooks: 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 Iterable MCP Server. Nothing to install.
get_webhooks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_webhooks 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 get_webhooks. 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.
get_webhooks is provided by the Iterable MCP Server MCP server (iterable/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Iterable MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
78 Iterable MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.