search_workflows
Search for workflows by name, description, or tags. Searches your own workflows.
This record as markdown: /tools/flowdot-llc-mcp-server/search-workflows.md
What search_workflows does on FlowDot MCP Server
AI agents call search_workflows 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.
Why search_workflows is rated Low
This tool retrieves and queries workflow data without creating, modifying, deleting, or executing anything. It is a standard search/query operation with no destructive or side-effect capabilities, placing it firmly in the Read category. The low severity reflects that search results contain only information the user already owns access to.
From the tool's definition Tool name 'search_workflows' and description 'Search for workflows by name, description, or tags' indicate a read-only search operation. The phrase 'Searches your own workflows' confirms retrieval with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs search_workflows 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 search_workflows, this is the rule to start with:
search_workflows is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every search_workflows call is checked against it from then on.
Questions about search_workflows
Search for workflows by name, description, or tags. Searches your own workflows. It is categorised as a Read tool in the FlowDot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for search_workflows: 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.
search_workflows 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 search_workflows 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 search_workflows. 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.
search_workflows 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.
More on FlowDot MCP Server, and thousands of servers like it.
This server
Across the catalogue