meta_webhook_status

SERVERHermoso SOURCEhttps://app.hermoso.ai/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/hermoso/meta-webhook-status.md

WHAT IT DOES

What meta_webhook_status does on Hermoso

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

RISK

Why meta_webhook_status is rated Low

Even though meta_webhook_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs meta_webhook_status safely

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

meta_webhook_status Allowed

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

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

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

FAQ

Questions about meta_webhook_status

What does the meta_webhook_status tool do? +

What Meta ACTUALLY has recorded for this app on a Page — the fields it will push, read straight back from Meta rather than from anything we stored. CHECK THIS BEFORE CONCLUDING THAT WEBHOOKS ARE NOT WORKING: an unsubscribed Page is completely silent and looks identical to a quiet one, so an empty event feed is not evidence of anything until you have seen the subscription. Read-only, 0 credits. It is categorised as a Read tool in the Hermoso MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on meta_webhook_status? +

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

What risk level is meta_webhook_status? +

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

Can I rate-limit meta_webhook_status? +

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

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

meta_webhook_status is provided by the Hermoso MCP server (https://app.hermoso.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hermoso, and thousands of servers like it.

This server

All 896 Hermoso tools →

Across the catalogue

claude_git_status on Claude Bridge → The MCP Attack Database →

Guides

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