Retrieve all orders between two dates (inclusive).
AI agents call orders_between_dates to retrieve information from MCP GraphQL Sales Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical order records filtered by a date range. It performs a read-only query against the sales database with no capability to create, modify, delete, or execute arbitrary code. The parameters (date range) are bounded and safe. Misuse would result in unauthorized data access rather than financial loss or system compromise, warranting 'low' severity.
From the tool's definition Tool name 'orders_between_dates' and description 'Retrieve all orders between two dates (inclusive)' indicate a query operation that fetches data without modification or side effects.
Attacks that exploit this kind of access
Retrieve all orders between two dates (inclusive). It is categorised as a Read tool in the MCP GraphQL Sales Server MCP Server, which means it retrieves data without modifying state.
Register the MCP GraphQL Sales Server MCP server in PolicyLayer and add a rule for orders_between_dates: 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 GraphQL Sales Server. Nothing to install.
orders_between_dates 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 orders_between_dates 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 orders_between_dates. 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.
orders_between_dates is provided by the MCP GraphQL Sales Server MCP server (jambelg/mcp-graphql-claude). 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 →