AI agents call compare_on_axis to retrieve information from Epicure MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to be a read-only query function that compares ingredients or flavor profiles along a specific axis (e.g., spice level, sweetness) using embedding analysis. No modification, execution, deletion, or financial action is indicated.
From the tool's definition Tool name 'compare_on_axis' with context of sibling tools (find_pairings, flavour_correlations, ingredient_on_factor, neighbors, pairing_score) and server description emphasizing 'read-only' access for 'ingredient pairings, flavor profiling, and culinary…
Documented attack patterns abuse exactly the kind of access compare_on_axis gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Epicure MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for compare_on_axis:
{
"version": "1",
"default": "deny",
"tools": {
"compare_on_axis": {}
}
}compare_on_axis 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.
compare_on_axis. It is categorised as a Read tool in the Epicure MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Epicure MCP Server MCP server in PolicyLayer and add a rule for compare_on_axis: 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 Epicure MCP Server. Nothing to install.
compare_on_axis 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 compare_on_axis 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 compare_on_axis. 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.
compare_on_axis is provided by the Epicure MCP Server MCP server (kaikaku-ai/epicure-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Epicure MCP Server, 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.
13 Epicure MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.