AI agents call cultural_profile 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.
The tool operates within a read-only ingredient-embedding model server that retrieves and analyzes culinary data without modifying or deleting anything. The description is empty, which slightly reduces confidence, but the server's read-only nature and the pattern of sibling tools strongly indicate this retrieves or queries cultural profile data. No side effects, no data modification, no execution risk.
From the tool's definition Tool name 'cultural_profile' belongs to a read-only MCP server described as offering tools for 'ingredient pairings, flavor profiling, and culinary exploration via cosine similarity and other embedding analyses.' The server is explicitly stated to be…
Documented attack patterns abuse exactly the kind of access cultural_profile 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 cultural_profile:
{
"version": "1",
"default": "deny",
"tools": {
"cultural_profile": {}
}
}cultural_profile 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.
cultural_profile. 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 cultural_profile: 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.
cultural_profile 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 cultural_profile 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 cultural_profile. 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.
cultural_profile 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.