Query with date range filtering on any date column. Supports grouping by time period (day, week, month, quarter, year).
AI agents call query_with_date_range to retrieve information from Parquet 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 filters existing data within a date range and groups results by time periods. It has no side effects—no data is created, modified, deleted, or executed.
From the tool's definition Tool name 'query_with_date_range' and description 'Query with date range filtering on any date column. Supports grouping by time period' indicate a read-only operation that retrieves and filters data without modification.
Attacks that exploit this kind of access
Query with date range filtering on any date column. Supports grouping by time period (day, week, month, quarter, year). It is categorised as a Read tool in the Parquet MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Parquet MCP Server MCP server in PolicyLayer and add a rule for query_with_date_range: 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 Parquet MCP Server. Nothing to install.
query_with_date_range 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 query_with_date_range 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 query_with_date_range. 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.
query_with_date_range is provided by the Parquet MCP Server MCP server (markmhendrickson/mcp-server-parquet). 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 →