get_orders_by_status
AI agents call get_orders_by_status 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.
This tool retrieves or queries order data based on status filters. It has no side effects—it does not create, modify, delete, or execute external operations. The 'get_' prefix and absence of mutation language confirm it is a Read operation.
From the tool's definition Tool name 'get_orders_by_status' is a getter that retrieves orders filtered by status. The description is empty, but the naming convention and sibling tools (get_customer_orders, get_dashboard_stats) suggest it queries existing data without modification.
Attacks that exploit this kind of access
get_orders_by_status. 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_orders_by_status: 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_orders_by_status 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_orders_by_status 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_orders_by_status. 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_orders_by_status 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 →