Medium Risk

meal_plan_week

7-day plan.

Part of the Spoonacular server.

meal_plan_week can modify Spoonacular data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SPOONACULAR →

Free to start. No card required.

AI agents use meal_plan_week to create or modify resources in Spoonacular. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call meal_plan_week repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Spoonacular.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "meal_plan_week": {
      "limits": [
        {
          "counter": "meal_plan_week_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Spoonacular policy for all 38 tools.

Get this rule live on your own Spoonacular server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SPOONACULAR →

View all 38 tools →

These attack patterns abuse exactly the kind of access meal_plan_week gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so meal_plan_week only ever does what you allow.

SECURE SPOONACULAR →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the meal_plan_week tool do? +

7-day plan.. It is categorised as a Write tool in the Spoonacular MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on meal_plan_week? +

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

What risk level is meal_plan_week? +

meal_plan_week is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit meal_plan_week? +

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

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

meal_plan_week is provided by the Spoonacular MCP server (https://gateway.pipeworx.io/spoonacular/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Spoonacular tool call.

Deterministic rules across all 38 Spoonacular tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.