AI agents use bottle_reply to create or update resources in Cartridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cartridge environment.
The tool sends a reply to an existing 'bottle' (message/conversation entity), which is a write operation that creates new data (a reply message). It modifies state reversibly by adding a response to an existing item. Severity is medium as misuse could send unintended messages in conversations.
From the tool's definition Reply to a specific bottle
Attacks that exploit this kind of access
Reply to a specific bottle. It is categorised as a Write tool in the Cartridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cartridge MCP server in PolicyLayer and add a rule for bottle_reply: 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 Cartridge. Nothing to install.
bottle_reply 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 bottle_reply 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 bottle_reply. 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.
bottle_reply is provided by the Cartridge MCP server (lucineer/cartridge-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 →