List DigiKey orders within a date range.
AI agents call list_orders to retrieve information from DigiKey MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical order data from DigiKey's systems. It performs no creation, modification, deletion, or execution of external operations. The data returned is read-only historical information. While financial data, the tool merely reads/retrieves it without moving money or creating financial obligations.
From the tool's definition Tool name 'list_orders' combined with description 'List DigiKey orders within a date range' indicates a retrieval operation. The verb 'list' and 'within a date range' query parameter are hallmarks of data retrieval with no modification capabilities.
Attacks that exploit this kind of access
List DigiKey orders within a date range. It is categorised as a Read tool in the DigiKey MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DigiKey MCP Server 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 DigiKey MCP Server. 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 DigiKey MCP Server MCP server (simon-77/digikey-mcp). 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 →