compare_datasets
AI agents call compare_datasets to retrieve information from Données Québec MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A 'compare_datasets' operation in an open data analysis context most naturally means retrieving and examining data from two datasets side-by-side for analytical purposes. No indication of modification, deletion, code execution, or financial operations. Low severity because comparison is a benign read-only operation with no side effects.
From the tool's definition Tool name 'compare_datasets' and server context (open data exploration/analysis) indicate data retrieval. Description is empty, which reduces specificity, but sibling tools (find_and_query, get_dataset_info, get_geospatial_features) are all Read operations,…
Attacks that exploit this kind of access
compare_datasets. It is categorised as a Read tool in the Données Québec MCP MCP Server, which means it retrieves data without modifying state.
Register the Données Québec 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 Données Québec MCP. 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 Données Québec MCP server (stefen-taime/donneesqc-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 →