AI agents call basketeer_orders_list to retrieve information from Basketeer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about pending orders without altering any data. It is a straightforward retrieval operation that poses minimal risk if misused by an AI agent, as it only exposes order visibility without enabling any side effects, financial transactions, or destructive actions.
From the tool's definition Tool name 'basketeer_orders_list' and description 'List upcoming (pending) orders' indicate a retrieval operation with no data modification. The verb 'List' and the absence of any mutation language (create, update, delete, modify) confirm read-only behavior.
Attacks that exploit this kind of access
List upcoming (pending) orders with their items, slot, and amend window. It is categorised as a Read tool in the Basketeer MCP Server, which means it retrieves data without modifying state.
Register the Basketeer MCP server in PolicyLayer and add a rule for basketeer_orders_list: 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 Basketeer. Nothing to install.
basketeer_orders_list 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 basketeer_orders_list 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 basketeer_orders_list. 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.
basketeer_orders_list is provided by the Basketeer MCP server (tobyandrews1985/basketeer). 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 →