Trigger a test for one household webhook.
AI agents invoke test_household_webhook to trigger actions in Mealie MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers a webhook, which causes an external HTTP request or event to be fired. This is an Execute-category action because it initiates an external operation whose effects depend on the webhook configuration. The blast radius is medium since it could trigger downstream automations or integrations depending on what the webhook is connected to.
From the tool's definition 'Trigger a test for one household webhook' — triggers an external operation (webhook execution)
Attacks that exploit this kind of access
Trigger a test for one household webhook. It is categorised as a Execute tool in the Mealie MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mealie MCP Server MCP server in PolicyLayer and add a rule for test_household_webhook: 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 Mealie MCP Server. Nothing to install.
test_household_webhook is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the test_household_webhook 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 test_household_webhook. 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.
test_household_webhook is provided by the Mealie MCP Server MCP server (nikopol666/mealie-mcp). 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 →