Get a date-price grid for a route showing the lowest flight price for each day. Returns an array of dates with their lowest prices, plus the overall cheapest date. Great for deal-hunting when the user has flexibility on travel dates — call this first to find the cheapest day, then use search_flig...
AI agents call get_date_grid to retrieve information from Pointsyeah without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries flight price information to help users find cheaper travel dates. It is purely informational retrieval with no side effects, reversible operations, code execution, or irreversible actions. The read-only nature ('call this first to find the cheapest day') confirms it is a data retrieval tool with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states it 'Get[s] a date-price grid' and 'Returns an array of dates with their lowest prices' — it retrieves and displays flight pricing data without modification, creation, deletion, code execution, or financial transaction.
Attacks that exploit this kind of access
Get a date-price grid for a route showing the lowest flight price for each day. Returns an array of dates with their lowest prices, plus the overall cheapest date. Great for deal-hunting when the user has flexibility on travel dates — call this first to find the cheapest day, then use search_flights on that date. The grid typically covers ~60 days around the anchor date. It is categorised as a Read tool in the Pointsyeah MCP Server, which means it retrieves data without modifying state.
Register the Pointsyeah MCP server in PolicyLayer and add a rule for get_date_grid: 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 Pointsyeah. Nothing to install.
get_date_grid 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 get_date_grid 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 get_date_grid. 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.
get_date_grid is provided by the Pointsyeah MCP server (slack-workspace-mcp-server). 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 →