mealie_webhooks_create
AI agents use mealie_webhooks_create to create or update resources in Mealie MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mealie MCP Server environment.
Webhook creation modifies system configuration by adding event handlers that trigger external operations. This is a Write action (reversible via deletion) rather than Execute, as the tool itself creates the webhook configuration—execution of the webhook payload depends on future events.
From the tool's definition Tool name 'mealie_webhooks_create' indicates creation of webhooks. Sibling tools show create/update/delete patterns on categories and comments. No description provided, but 'create' suffix and webhook context indicate data modification.
Attacks that exploit this kind of access
mealie_webhooks_create. It is categorised as a Write tool in the Mealie MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mealie MCP Server MCP server in PolicyLayer and add a rule for mealie_webhooks_create: 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.
mealie_webhooks_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mealie_webhooks_create 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 mealie_webhooks_create. 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.
mealie_webhooks_create is provided by the Mealie MCP Server MCP server (mdlopresti/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 →