get_filtered_orders
AI agents call get_filtered_orders to retrieve information from Restaurant Backend MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and 'filtered_orders' noun phrase are standard patterns for data retrieval operations. No side effects or mutations are implied. The tool fits the Read category (retrieves or queries data; no side effects). Severity is low since querying order data poses minimal risk compared to creating, deleting, or financial operations.
From the tool's definition Tool name 'get_filtered_orders' indicates retrieval/query functionality. Description is empty, but name and sibling tools context (create_order, get_customer_orders) strongly suggest this retrieves order data without modification.
Attacks that exploit this kind of access
get_filtered_orders. It is categorised as a Read tool in the Restaurant Backend MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Restaurant Backend MCP Server MCP server in PolicyLayer and add a rule for get_filtered_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 Restaurant Backend MCP Server. Nothing to install.
get_filtered_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 get_filtered_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 get_filtered_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.
get_filtered_orders is provided by the Restaurant Backend MCP Server MCP server (pasanis/mcp-server). 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 →