Low Risk

get_restaurant_menu

Get a restaurant

How to control get_restaurant_menu ↓

What get_restaurant_menu does on Food402

AI agents call get_restaurant_menu 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.

Low Risk

Why get_restaurant_menu needs a policy

This tool retrieves restaurant menu information to enable users to browse options. It has no side effects, does not modify data, does not execute code or external operations, and does not involve financial transactions or destructive actions. It is purely informational, making it a Read category tool with low severity.

From the tool's definition Tool name 'get_restaurant_menu' and description 'Get a restaurant' indicate retrieval of menu data without modification, deletion, or execution of external actions.

Documented attack patterns abuse exactly the kind of access get_restaurant_menu gives an agent:

How to control get_restaurant_menu

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_restaurant_menu:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_restaurant_menu": {}
  }
}

get_restaurant_menu is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Food402 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_restaurant_menu

What does the get_restaurant_menu tool do? +

Get a restaurant. It is categorised as a Read tool in the Food402 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_restaurant_menu? +

Register the Food402 MCP server in PolicyLayer and add a rule for get_restaurant_menu: 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.

What risk level is get_restaurant_menu? +

get_restaurant_menu is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_restaurant_menu? +

Yes. Add a rate_limit block to the get_restaurant_menu 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.

How do I block get_restaurant_menu completely? +

Set action: deny in the PolicyLayer policy for get_restaurant_menu. 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.

What MCP server provides get_restaurant_menu? +

get_restaurant_menu 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.

Enforce policy on every Food402 tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.