Browse recipe and tutorial pages from Reflex docs.
AI agents call list_recipes to retrieve information from Reflex Docs 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 and lists recipe/tutorial documentation from a static documentation server. It performs a read-only query operation with no side effects, no code execution, and no data modification. The blast radius of misuse is minimal—an AI agent could only retrieve documentation pages that are already publicly available.
From the tool's definition Tool name 'list_recipes' and description 'Browse recipe and tutorial pages from Reflex docs' indicate retrieval and listing of documentation content with no modification or execution capability.
Attacks that exploit this kind of access
Browse recipe and tutorial pages from Reflex docs. It is categorised as a Read tool in the Reflex Docs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Reflex Docs MCP Server MCP server in PolicyLayer and add a rule for list_recipes: 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 Reflex Docs MCP Server. Nothing to install.
list_recipes 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_recipes 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_recipes. 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_recipes is provided by the Reflex Docs MCP Server MCP server (itsmeadarsh2008/reflex-docs-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 →