Get sections by cookbook ID. CookbookIds are globally unique and can be found through the cookbooks tool.
AI agents call sections_by_cookbook_id to retrieve information from Saffron MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing section data associated with a cookbook using its ID. It performs a read-only query operation with no data creation, modification, deletion, or external execution. The 'Get' verb and retrieval-focused description confirm this is a Read category tool with low severity, as it only accesses structured recipe/cookbook metadata.
From the tool's definition Tool name and description indicate 'Get sections by cookbook ID' - a retrieval operation that queries data without modification or side effects.
Attacks that exploit this kind of access
Get sections by cookbook ID. CookbookIds are globally unique and can be found through the cookbooks tool. It is categorised as a Read tool in the Saffron MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Saffron MCP Server MCP server in PolicyLayer and add a rule for sections_by_cookbook_id: 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 Saffron MCP Server. Nothing to install.
sections_by_cookbook_id 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 sections_by_cookbook_id 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 sections_by_cookbook_id. 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.
sections_by_cookbook_id is provided by the Saffron MCP Server MCP server (tvh/saffron-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 →