Low Risk

lookup_order

Look up one or more orders by origin_id (client_id)

How to control lookup_order ↓

What lookup_order does on Mcp Ap2

AI agents call lookup_order to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why lookup_order needs a policy

The tool queries/retrieves order information based on a client ID. This is a read-only operation with no side effects—it does not create, modify, delete, or execute anything. While it operates in a payment protocol context, the tool itself merely looks up existing data rather than moving money or creating financial obligations.

From the tool's definition Tool name 'lookup_order' and description 'Look up one or more orders by origin_id (client_id)' indicate a retrieval operation with no modification of data.

Documented attack patterns abuse exactly the kind of access lookup_order gives an agent:

How to control lookup_order

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for lookup_order:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "lookup_order": {}
  }
}

lookup_order is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Ap2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about lookup_order

What does the lookup_order tool do? +

Look up one or more orders by origin_id (client_id). It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lookup_order? +

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

What risk level is lookup_order? +

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

Can I rate-limit lookup_order? +

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

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

lookup_order is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.