AI agents call ingredient_on_factor 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 is a read-only MCP server for culinary ingredient analysis. The tool name pattern and context indicate it retrieves or queries ingredient properties along specific factors (likely returning embedding-based scores or profiles). No side effects, modifications, or external operations are implied.
From the tool's definition Tool name 'ingredient_on_factor' suggests a query operation; server description explicitly states 'read-only' nature.
Documented attack patterns abuse exactly the kind of access ingredient_on_factor 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 ingredient_on_factor:
{
"version": "1",
"default": "deny",
"tools": {
"ingredient_on_factor": {}
}
}ingredient_on_factor 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.
ingredient_on_factor. 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 ingredient_on_factor: 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.
ingredient_on_factor 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 ingredient_on_factor 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 ingredient_on_factor. 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.
ingredient_on_factor 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.