search_orders
AI agents call search_orders to retrieve information from FleetMind MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'search_orders' clearly denotes a read operation that queries existing order data. Even without explicit documentation, 'search' is unambiguously a retrieval action. There is no indication of modification, deletion, or execution of external operations. Confidence is slightly reduced (0.8 rather than 0.95+) due to empty description, but the name itself is sufficiently clear.
From the tool's definition Tool name 'search_orders' indicates a query/retrieval operation. No description provided, but the verb 'search' strongly suggests data retrieval with no side effects.
Attacks that exploit this kind of access
search_orders. It is categorised as a Read tool in the FleetMind MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FleetMind MCP Server MCP server in PolicyLayer and add a rule for search_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 FleetMind MCP Server. Nothing to install.
search_orders 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_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.
Set action: deny in the PolicyLayer policy for search_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.
search_orders is provided by the FleetMind MCP Server MCP server (mashrur-rahman-fahim/fleetmind-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 →