Run the group foods seeder using a Mealie-native payload.
AI agents invoke seed_group_foods 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 executes a seeder operation rather than simply reading or writing individual records. Seeders typically perform bulk initialization or population of data and their effects depend on the payload provided. While not immediately destructive (data can likely be rolled back), it is an executable operation that modifies system state at scale, making it more severe than simple Write operations.
From the tool's definition Tool runs a seeder operation ('Run the group foods seeder') which triggers external data manipulation in Mealie.
Attacks that exploit this kind of access
Run the group foods seeder using a Mealie-native payload. 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 seed_group_foods: 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.
seed_group_foods 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 seed_group_foods 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 seed_group_foods. 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.
seed_group_foods 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 →