Set order note and service preferences. Call before place_order.
AI agents use set_order_note to create or update resources in Food402 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Food402 environment.
This tool creates or modifies order metadata (notes and preferences) reversibly—the changes can be edited or removed before order placement. It does not execute payment (Financial), delete data (Destructive), or trigger external operations beyond recording user preferences (Execute).
From the tool's definition Tool description states it sets order notes and service preferences, which are metadata modifications to an order before placement. The tool modifies order state (notes/preferences) without executing the final transaction or deleting data.
Documented attack patterns abuse exactly the kind of access set_order_note gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Food402, and nothing reaches the server without passing your rules. This is the rule we recommend for set_order_note:
{
"version": "1",
"default": "deny",
"tools": {
"set_order_note": {
"limits": [
{
"counter": "set_order_note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_order_note 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.
Free to start. No card required.
Set order note and service preferences. Call before place_order. It is categorised as a Write tool in the Food402 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Food402 MCP server in PolicyLayer and add a rule for set_order_note: 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 Food402. Nothing to install.
set_order_note 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 set_order_note 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 set_order_note. 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.
set_order_note is provided by the Food402 MCP server (rersozlu/food402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Food402, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 Food402 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.