AI agents call get_orders 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 retrieves existing order information without modifying, deleting, or executing external operations. It fits the Read category pattern of querying data with no side effects. Severity is low because order history retrieval poses minimal risk even if misused by an AI agent—it exposes user data but does not enable financial transactions, destructive actions, or code execution.
From the tool's definition Tool name 'get_orders' and context indicates retrieval of user order data. Description is incomplete ('Get user') but the naming pattern and sibling tools (get_addresses, get_basket, get_cities) all perform read operations without modification.
Documented attack patterns abuse exactly the kind of access get_orders 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_orders:
{
"version": "1",
"default": "deny",
"tools": {
"get_orders": {}
}
}get_orders 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_orders: 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_orders 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_orders 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_orders. 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_orders 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.