Find datasets related to a given dataset by shared tags and organization.
AI agents call find_related_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 is a read-only discovery operation that retrieves dataset metadata based on search criteria (tags, organization). It has no side effects, does not execute code, does not modify data, and does not involve financial operations. The blast radius of misuse is minimal—an agent might retrieve metadata about related datasets, but cannot alter or delete them.
From the tool's definition The tool 'find_related_datasets' discovers and retrieves information about datasets by searching through shared tags and organization attributes.
Attacks that exploit this kind of access
Find datasets related to a given dataset by shared tags and organization. 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 find_related_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.
find_related_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 find_related_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 find_related_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.
find_related_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 →