theprotocol_getSupportedWebhookEvents
List all event types you can subscribe to via createWebhook (42+ types).
This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-getsupportedwebhookevents.md
What theprotocol_getSupportedWebhookEvents does on TheProtocol — Sovereign AI Agent Platform
AI agents call theprotocol_getSupportedWebhookEvents to retrieve information from TheProtocol — Sovereign AI Agent Platform without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why theprotocol_getSupportedWebhookEvents is rated Low
This is a pure read operation that enumerates supported webhook events. It has no write, execute, destructive, or financial impact. An AI agent misusing this tool could at worst discover event types it shouldn't subscribe to, but the tool itself does not commit those subscriptions or trigger any external operations. Blast radius is minimal.
From the tool's definition Tool name contains 'get' and description states 'List all event types' — a retrieval operation with no side effects. The tool queries available webhook event types without modifying, creating, or deleting data.
Attacks that exploit this kind of access
The rule that runs theprotocol_getSupportedWebhookEvents safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TheProtocol — Sovereign AI Agent Platform, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For theprotocol_getSupportedWebhookEvents, this is the rule to start with:
theprotocol_getSupportedWebhookEvents is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect TheProtocol — Sovereign AI Agent Platform, apply this rule, and every theprotocol_getSupportedWebhookEvents call is checked against it from then on.
Questions about theprotocol_getSupportedWebhookEvents
List all event types you can subscribe to via createWebhook (42+ types). It is categorised as a Read tool in the TheProtocol — Sovereign AI Agent Platform MCP Server, which means it retrieves data without modifying state.
Register the TheProtocol — Sovereign AI Agent Platform MCP server in PolicyLayer and add a rule for theprotocol_getSupportedWebhookEvents: 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 TheProtocol — Sovereign AI Agent Platform. Nothing to install.
theprotocol_getSupportedWebhookEvents 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 theprotocol_getSupportedWebhookEvents 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 theprotocol_getSupportedWebhookEvents. 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.
theprotocol_getSupportedWebhookEvents is provided by the TheProtocol — Sovereign AI Agent Platform MCP server (https://api.theprotocol.cloud/mcp/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TheProtocol — Sovereign AI Agent Platform, and thousands of servers like it.
Across the catalogue