Check if a dataset is current by comparing its update frequency to its last modification date.
AI agents call check_freshness to retrieve information from Ontario Data without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes metadata about a dataset (update frequency and modification date) to provide informational status. It has no side effects, does not modify data, execute code, delete resources, or move money. It is a pure read operation that queries dataset metadata to assess freshness.
From the tool's definition The tool 'check_freshness' performs a comparison operation between a dataset's update frequency and last modification date to determine currency status.
Attacks that exploit this kind of access
Check if a dataset is current by comparing its update frequency to its last modification date. It is categorised as a Read tool in the Ontario Data MCP Server, which means it retrieves data without modifying state.
Register the Ontario Data MCP server in PolicyLayer and add a rule for check_freshness: 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 Ontario Data. Nothing to install.
check_freshness 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 check_freshness 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 check_freshness. 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.
check_freshness is provided by the Ontario Data MCP server (sprine/ontario-data-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 →