search_datasets
AI agents call search_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 appears to search or query available datasets from Ontario's open data portals. It retrieves information to help users discover datasets without modifying, deleting, or executing arbitrary code. No side effects indicated. Classified as Read due to its discovery/search nature matching the server's stated purpose of 'discovering datasets'.
From the tool's definition Tool name 'search_datasets' with sibling tools including 'find_related_datasets', 'get_dataset_info', 'list_geo_datasets', 'list_organizations' suggests querying/discovery operations. Server description emphasizes 'discovering' and 'querying' datasets.
Attacks that exploit this kind of access
search_datasets. 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 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 Ontario Data. 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 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 →