Compare metadata side-by-side for multiple datasets (can be cross-portal).
AI agents call compare_datasets 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 displays metadata information about datasets across portals for comparative analysis. It has no side effects, does not modify data, does not execute queries or code, and does not delete anything. It is a read-only operation that fits squarely within the 'Read' category as a data retrieval and comparison function.
From the tool's definition Tool performs comparison of dataset metadata 'side-by-side' for multiple datasets. Described action is purely informational—retrieving and presenting metadata for analysis without modification, deletion, or execution of code/commands.
Attacks that exploit this kind of access
Compare metadata side-by-side for multiple datasets (can be cross-portal). 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 compare_datasets: 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.
compare_datasets 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 compare_datasets 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 compare_datasets. 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.
compare_datasets 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 →