Get list of webhooks for a form.
AI agents call get_form_webhooks to retrieve information from JotForm API Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple query to list webhooks associated with a form. It retrieves data without side effects, matching the Read category definition. The severity is low because webhook configuration metadata poses minimal risk if exposed to an AI agent—no financial obligations, no destructive operations, and no code execution is triggered by this retrieval alone.
From the tool's definition Tool name 'get_form_webhooks' combined with description 'Get list of webhooks for a form' indicates a retrieval operation that returns existing webhook configuration data without modification or execution.
Attacks that exploit this kind of access
Get list of webhooks for a form. It is categorised as a Read tool in the JotForm API Server MCP Server, which means it retrieves data without modifying state.
Register the JotForm API Server MCP server in PolicyLayer and add a rule for get_form_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 JotForm API Server. Nothing to install.
get_form_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_form_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_form_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_form_webhooks is provided by the JotForm API Server MCP server (the-ai-workshops/jotform-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 →