AI agents call list_factors 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.
Despite an empty description, the tool name 'list_factors' indicates retrieval of ingredient factors or dimensions from the embedding model. This aligns with the server's stated read-only nature and analytical purpose. No modification, deletion, code execution, or financial impact is suggested.
From the tool's definition Tool name 'list_factors' combined with server context describing a 'read-only MCP server' offering 'embedding analyses' and 'culinary exploration'; sibling tools include 'find_pairings', 'flavor_correlations', 'cultural_profile' suggesting data retrieval…
Documented attack patterns abuse exactly the kind of access list_factors 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 list_factors:
{
"version": "1",
"default": "deny",
"tools": {
"list_factors": {}
}
}list_factors 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.
list_factors. 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 list_factors: 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.
list_factors 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 list_factors 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 list_factors. 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.
list_factors 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.