browse_recipes

Browse public agent recipes shared by other users. Search by name, category, or tags.

SERVERFlowDot MCP Server SOURCEflowdot-llc/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/flowdot-llc-mcp-server/browse-recipes.md

WHAT IT DOES

What browse_recipes does on FlowDot MCP Server

AI agents call browse_recipes to retrieve information from FlowDot MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why browse_recipes is rated Low

This tool retrieves and searches publicly available recipes without creating, modifying, executing, or deleting data. It is a read-only operation that queries metadata about community-shared recipes. The blast radius of misuse is minimal—an agent could only retrieve information already marked as public.

From the tool's definition Tool description states 'Browse public agent recipes' and 'Search by name, category, or tags' — these are query and retrieval operations with no modification or execution of workflows.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browse_recipes safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browse_recipes, this is the rule to start with:

browse_recipes Allowed

browse_recipes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browse_recipes": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every browse_recipes call is checked against it from then on.

FAQ

Questions about browse_recipes

What does the browse_recipes tool do? +

Browse public agent recipes shared by other users. Search by name, category, or tags. It is categorised as a Read tool in the FlowDot MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browse_recipes? +

Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for browse_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 FlowDot MCP Server. Nothing to install.

What risk level is browse_recipes? +

browse_recipes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browse_recipes? +

Yes. Add a rate_limit block to the browse_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.

How do I block browse_recipes completely? +

Set action: deny in the PolicyLayer policy for browse_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.

What MCP server provides browse_recipes? +

browse_recipes is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FlowDot MCP Server, and thousands of servers like it.

This server

All 207 FlowDot MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →