create_ingredient · Bar Assistant MCP Server MCP

WHAT IT DOES

What create_ingredient does on Bar Assistant MCP Server

AI agents use create_ingredient to create or update resources in Bar Assistant MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bar Assistant MCP Server environment.

WHY IT NEEDS A POLICY

Why create_ingredient needs a policy

This tool creates new records in a bar inventory database. It is a Write operation because it creates or modifies data reversibly—new ingredients can be deleted or updated without permanent loss. There is no financial impact, no code execution, and no destructive operations. The severity is low because misuse would only affect local bar inventory data with minimal blast radius.

From the tool's definition Tool name 'create_ingredient' and description 'Create a new ingredient in the bar database' indicate reversible data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_ingredient Rate-limited

create_ingredient stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_ingredient": {
      "limits": [
        {
          "counter": "create_ingredient_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Bar Assistant MCP Server, so you can run agents against it safely.

FAQ

Questions about create_ingredient

What does the create_ingredient tool do? +

Create a new ingredient in the bar database. Use this when an ingredient doesn. It is categorised as a Write tool in the Bar Assistant MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_ingredient? +

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

What risk level is create_ingredient? +

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

Can I rate-limit create_ingredient? +

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

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

create_ingredient is provided by the Bar Assistant MCP Server MCP server (the-real-py/bar-assistant-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.