AI agents call find_relevant_datasets to retrieve information from Toronto MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or searches dataset metadata from a public CKAN data portal. It performs no modifications, deletions, or external operations. Even though the description is empty, the tool name and consistent pattern of read-only verbs ('find', 'search', 'list', 'get') among siblings, combined with the server's stated purpose of 'querying, analyzing, and retrieving datasets', strongly indicates a Read operation…
From the tool's definition Tool name 'find_relevant_datasets' and sibling tools like 'search_datasets', 'list_datasets', 'get_package', 'get_resource_records' all indicate read-only query operations against Toronto's open data portal.
Documented attack patterns abuse exactly the kind of access find_relevant_datasets gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Toronto MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for find_relevant_datasets:
{
"version": "1",
"default": "deny",
"tools": {
"find_relevant_datasets": {}
}
}find_relevant_datasets is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
find_relevant_datasets. It is categorised as a Read tool in the Toronto MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Toronto MCP Server MCP server in PolicyLayer and add a rule for find_relevant_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 Toronto MCP Server. Nothing to install.
find_relevant_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_relevant_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_relevant_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_relevant_datasets is provided by the Toronto MCP Server MCP server (toronto-inc/toronto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Toronto MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Toronto MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.