search_flow_orders

Find existing Sanka orders by customer name, order notes, or line-item name/description in the connected workspace. Returns 20 matches per page. Ask the user to choose when several orders match; never choose by guesswork. Use the chosen order_id with preview_flow_invoice before requesting confirm...

SERVERSanka MCP Server SOURCEsankahq/sanka-mcp

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/sankahq-sanka-mcp/search-flow-orders.md

WHAT IT DOES

What search_flow_orders does on Sanka MCP Server

AI agents call search_flow_orders to retrieve information from Sanka 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 search_flow_orders is rated Low

Even though search_flow_orders only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_flow_orders safely

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

search_flow_orders Allowed

search_flow_orders 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": {
    "search_flow_orders": {}
  }
}

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

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

FAQ

Questions about search_flow_orders

What does the search_flow_orders tool do? +

How do I enforce a policy on search_flow_orders? +

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

What risk level is search_flow_orders? +

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

Can I rate-limit search_flow_orders? +

Yes. Add a rate_limit block to the search_flow_orders 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 search_flow_orders completely? +

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

search_flow_orders is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

All 385 Sanka MCP Server tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

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