AI agents call flavour_correlations 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 retrieve or analyze flavor correlation data from the Epicure embedding model, consistent with the server's stated read-only, analytical purpose. No side effects, modifications, or destructive operations are indicated. The empty description slightly reduces confidence, but context from sibling tools and server purpose strongly indicates a data retrieval function.
From the tool's definition Tool is part of a 'read-only MCP server' for 'culinary exploration' and 'embedding analyses'. Sibling tools (closest_mode, compare_on_axis, cultural_profile, find_pairings, neighbors, pairing_score) are all analytical/retrieval operations.
Documented attack patterns abuse exactly the kind of access flavour_correlations 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 flavour_correlations:
{
"version": "1",
"default": "deny",
"tools": {
"flavour_correlations": {}
}
}flavour_correlations 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.
flavour_correlations. 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 flavour_correlations: 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.
flavour_correlations 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 flavour_correlations 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 flavour_correlations. 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.
flavour_correlations 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.