AI agents call get_addresses to retrieve information from Food402 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing address information without creating, modifying, or deleting data. It has no side effects and poses minimal risk—it merely surfaces data the user already owns. Classified as Read with low severity.
From the tool's definition Tool name 'get_addresses' and context indicates it retrieves user address data. Description is truncated ('Get user') but the name and sibling tools (add_address, checkout_ready) confirm this is a data retrieval operation with no modification capability.
Documented attack patterns abuse exactly the kind of access get_addresses 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 get_addresses:
{
"version": "1",
"default": "deny",
"tools": {
"get_addresses": {}
}
}get_addresses is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get user. It is categorised as a Read tool in the Food402 MCP Server, which means it retrieves data without modifying state.
Register the Food402 MCP server in PolicyLayer and add a rule for get_addresses: 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.
get_addresses is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_addresses 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 get_addresses. 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.
get_addresses 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.