search_datasets
AI agents call search_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.
Despite having an empty description, the naming pattern (search_*) and context within a data exploration server strongly indicate this is a Read operation—it searches/queries datasets without modifying them. No shell execution, data deletion, or financial implications. Confidence is slightly reduced due to the empty description, but the pattern is clear.
From the tool's definition Tool name is 'search_datasets' and sits among sibling tools like 'find_and_query', 'get_dataset_info', 'get_catalog_stats', and 'describe_geospatial_layer', which are all exploratory/query operations.
Attacks that exploit this kind of access
search_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 search_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.
search_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 search_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 search_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.
search_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 →