Add a new delivery address. Use get_cities, get_districts, get_neighborhoods to find location IDs first.
AI agents use add_address 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 new persistent data (delivery addresses) that will be used in subsequent financial transactions (food orders). It is Write-category because it adds data reversibly—addresses can be deleted or modified later.
From the tool's definition add_address creates a new delivery address record in the system. The description explicitly states 'Add a new delivery address,' indicating irreversible data creation.
Documented attack patterns abuse exactly the kind of access add_address 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 add_address:
{
"version": "1",
"default": "deny",
"tools": {
"add_address": {
"limits": [
{
"counter": "add_address_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_address 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.
Add a new delivery address. Use get_cities, get_districts, get_neighborhoods to find location IDs first. 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 add_address: 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.
add_address 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 add_address 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 add_address. 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.
add_address 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.