AI agents call get_cooking_guidelines to retrieve information from Goodbook without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing cooking guidelines and standards from PDF documentation. It has no side effects—it does not create, modify, delete, or execute any operations. The server is explicitly designed to work with static PDF files containing reference information.
From the tool's definition Tool is described as 'Get cooking guidelines and standards' which retrieves information from PDF documents about food service standards and preparation guidelines.
Attacks that exploit this kind of access
Get cooking guidelines and standards for specific dishes or cooking methods. It is categorised as a Read tool in the Goodbook MCP Server, which means it retrieves data without modifying state.
Register the Goodbook MCP server in PolicyLayer and add a rule for get_cooking_guidelines: 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 Goodbook. Nothing to install.
get_cooking_guidelines 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 get_cooking_guidelines 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 get_cooking_guidelines. 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.
get_cooking_guidelines is provided by the Goodbook MCP server (whenyouarestrange/goodbook-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →