Medium Risk

cooking_convert_units

Convert between cooking measurement units — cups, tablespoons, grams, ounces, milliliters, and more. TRIGGERS: - 'how many grams in a cup', 'convert tablespoons to cups' - 'ounces to grams', 'ml to cups', 'teaspoons in a tablespoon' - 'metric to imperial', 'cooking conversions'

Part of the SAVORDISH server.

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

SECURE SAVORDISH →

Free to start. No card required.

AI agents use cooking_convert_units to create or modify resources in SAVORDISH. 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 cooking_convert_units 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 SAVORDISH.

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

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

See the full SAVORDISH policy for all 31 tools.

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

ENFORCE ON MY SAVORDISH →

View all 31 tools →

These attack patterns abuse exactly the kind of access cooking_convert_units 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 cooking_convert_units only ever does what you allow.

SECURE SAVORDISH →

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

What does the cooking_convert_units tool do? +

Convert between cooking measurement units — cups, tablespoons, grams, ounces, milliliters, and more. TRIGGERS: - 'how many grams in a cup', 'convert tablespoons to cups' - 'ounces to grams', 'ml to cups', 'teaspoons in a tablespoon' - 'metric to imperial', 'cooking conversions'. It is categorised as a Write tool in the SAVORDISH MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cooking_convert_units? +

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

What risk level is cooking_convert_units? +

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

Can I rate-limit cooking_convert_units? +

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

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

cooking_convert_units is provided by the SAVORDISH MCP server (savordish/savor-dish). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SAVORDISH tool call.

Deterministic rules across all 31 SAVORDISH 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.