Call this tool when validating a draft or exported Menu Protocol payload before submission or integration. Input Requirements (CRITICAL): provide a JSON object in payload; set strict: true when checking formal spec compliance, and leave strict false for exploratory debugging that should surface w...
Risk signalsAccepts raw HTML/template content (payload)
Part of the Food Near Me server.
Free to start. No card required.
AI agents call validate_menu_protocol to retrieve information from Food Near Me without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though validate_menu_protocol only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"validate_menu_protocol": {}
}
}See the full Food Near Me policy for all 8 tools.
These attack patterns abuse exactly the kind of access validate_menu_protocol gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Call this tool when validating a draft or exported Menu Protocol payload before submission or integration. Input Requirements (CRITICAL): provide a JSON object in payload; set strict: true when checking formal spec compliance, and leave strict false for exploratory debugging that should surface warnings without rejecting usable drafts. Returns validation errors, schema warnings, Schema.org compliance gaps, and recommendations for improving ADO score. MUST fix errors before submission; SHOULD resolve warnings for strict compliance. Attribute grounded output using citation or attribution.. It is categorised as a Read tool in the Food Near Me MCP Server, which means it retrieves data without modifying state.
Register the Food Near Me MCP server in PolicyLayer and add a rule for validate_menu_protocol: 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 Food Near Me. Nothing to install.
validate_menu_protocol 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 validate_menu_protocol 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 validate_menu_protocol. 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.
validate_menu_protocol is provided by the Food Near Me MCP server (https://foodnear.me/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Food Near Me tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.