webhook_listen_status

Report whether the inbound webhook listener is running, its endpoint, HMAC state, and hit count.

SERVERIconnect SOURCEiconnect-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/webhook-listen-status.md

WHAT IT DOES

What webhook_listen_status does on Iconnect

AI agents call webhook_listen_status to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why webhook_listen_status is rated Low

This tool retrieves and reports the current state of a webhook listener (running status, endpoint URL, HMAC configuration, and event hit count). It performs passive status inspection without modifying, creating, deleting, or executing any operations. No data is changed, no code is executed, and no irreversible actions occur.

From the tool's definition Tool name 'webhook_listen_status' and description 'Report whether the inbound webhook listener is running, its endpoint, HMAC state, and hit count' indicate status reporting and querying of webhook listener state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs webhook_listen_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For webhook_listen_status, this is the rule to start with:

webhook_listen_status Allowed

webhook_listen_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "webhook_listen_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every webhook_listen_status call is checked against it from then on.

FAQ

Questions about webhook_listen_status

What does the webhook_listen_status tool do? +

Report whether the inbound webhook listener is running, its endpoint, HMAC state, and hit count. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on webhook_listen_status? +

Register the Iconnect MCP server in PolicyLayer and add a rule for webhook_listen_status: 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 Iconnect. Nothing to install.

What risk level is webhook_listen_status? +

webhook_listen_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit webhook_listen_status? +

Yes. Add a rate_limit block to the webhook_listen_status 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.

How do I block webhook_listen_status completely? +

Set action: deny in the PolicyLayer policy for webhook_listen_status. 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.

What MCP server provides webhook_listen_status? +

webhook_listen_status is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 297 Iconnect tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →