searchWebhooksWithId

Searches webhooks with the specified criteria and pagination.

SERVERFusionauth SOURCE@fusionauth/mcp-api

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-fusionauth-mcp-api/searchwebhookswithid.md

WHAT IT DOES

What searchWebhooksWithId does on Fusionauth

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

RISK

Why searchWebhooksWithId is rated Low

This tool queries webhooks matching provided criteria and returns paginated results. The operation is read-only: it retrieves configuration data about webhooks without creating, modifying, deleting, or executing any changes. Blast radius is minimal as misuse exposes only webhook metadata that is already stored in the system.

From the tool's definition Tool name contains 'search' and description states 'Searches webhooks with the specified criteria and pagination' — both indicate data retrieval with no modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs searchWebhooksWithId safely

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

searchWebhooksWithId Allowed

searchWebhooksWithId 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": {
    "searchWebhooksWithId": {}
  }
}

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

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

FAQ

Questions about searchWebhooksWithId

What does the searchWebhooksWithId tool do? +

Searches webhooks with the specified criteria and pagination. It is categorised as a Read tool in the Fusionauth MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on searchWebhooksWithId? +

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

What risk level is searchWebhooksWithId? +

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

Can I rate-limit searchWebhooksWithId? +

Yes. Add a rate_limit block to the searchWebhooksWithId 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 searchWebhooksWithId completely? +

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

searchWebhooksWithId is provided by the Fusionauth MCP server (@fusionauth/mcp-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Fusionauth, and thousands of servers like it.

This server

All 314 Fusionauth tools →

Across the catalogue

The MCP Attack Database →

Guides

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