Check status of an order
AI agents call check_order_status to retrieve information from MCP A2A AP2 Food Delivery & Payments without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves order status information without modifying, executing external operations, or affecting financial state. It is a straightforward read operation. While the server handles payments and orders (which could introduce financial context), this specific tool only queries status.
From the tool's definition Tool name 'check_order_status' and description 'Check status of an order' indicate a retrieval operation with no side effects. The action is purely informational—querying the state of an existing order.
Attacks that exploit this kind of access
Check status of an order. It is categorised as a Read tool in the MCP A2A AP2 Food Delivery & Payments MCP Server, which means it retrieves data without modifying state.
Register the MCP A2A AP2 Food Delivery & Payments MCP server in PolicyLayer and add a rule for check_order_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 MCP A2A AP2 Food Delivery & Payments. Nothing to install.
check_order_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 check_order_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 check_order_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.
check_order_status is provided by the MCP A2A AP2 Food Delivery & Payments MCP server (tas1337/mcp-a2a-ap2-im-hungry). 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 →