list_orders
Bestellungen des verknuepften Kunden inkl. Status, Zahlstatus und Lieferstatus/Sendungsverfolgung. Erfordert ein via link_account verknuepftes token.
This record as markdown: /tools/de-tabak-brucker-www-shop/list-orders.md
What list_orders does on Shop
AI agents call list_orders to retrieve information from Shop without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max. Bestellungen (1-20, Default 10). |
suche | string | — | Optional: nach Auftragsnummer/Artikel filtern. |
token | string | Yes | session_token aus link_account (nach Browser-Login). |
Parameters from the server's own tool schema.
Why list_orders is rated Low
Even though list_orders only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
The rule that runs list_orders safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Shop, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_orders, this is the rule to start with:
list_orders is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Shop, apply this rule, and every list_orders call is checked against it from then on.
Questions about list_orders
Bestellungen des verknuepften Kunden inkl. Status, Zahlstatus und Lieferstatus/Sendungsverfolgung. Erfordert ein via link_account verknuepftes token. It is categorised as a Read tool in the Shop MCP Server, which means it retrieves data without modifying state.
list_orders accepts 3 parameters: limit, suche, token. Required: token. The full parameter table on this page comes from the server's own tool schema.
Register the Shop MCP server in PolicyLayer and add a rule for list_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 Shop. Nothing to install.
list_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 list_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 list_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.
list_orders is provided by the Shop MCP server (https://mcp.tabak-brucker.de/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Shop, and thousands of servers like it.
This server
Across the catalogue