open-canada.datasets.search
Search the Government of Canada open data catalog by free text, topic subject, and/or publishing department, returning dataset id, title, notes, organization, subjects, and release/modified dates. Use open-canada.subject_list or open-canada.organization_list to find valid filter slugs. Data: open...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/open-canada.datasets.search.md
What open-canada.datasets.search does on Apibase
AI agents use open-canada.datasets.search to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
rows | integer | — | Number of datasets to return (1-20, default 10) |
query | string | — | Free-text search across dataset title/description (e.g. "climate normals") |
subject | string | — | Topic slug to filter by (e.g. "health_and_safety", "nature_and_environment") — see open-canada.subject_list |
organization | string | — | Federal department/agency slug to filter by (e.g. "nrcan-rncan") — see open-canada.organization_list |
Parameters from the server's own tool schema.
Why open-canada.datasets.search is rated Medium
An AI agent can call open-canada.datasets.search faster than any human can review: one bad instruction and it creates or modifies resources in Apibase by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs open-canada.datasets.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For open-canada.datasets.search, this is the rule to start with:
open-canada.datasets.search stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every open-canada.datasets.search call is checked against it from then on.
Questions about open-canada.datasets.search
Search the Government of Canada open data catalog by free text, topic subject, and/or publishing department, returning dataset id, title, notes, organization, subjects, and release/modified dates. Use open-canada.subject_list or open-canada.organization_list to find valid filter slugs. Data: open.canada.ca CKAN Action API, no auth required. It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
open-canada.datasets.search accepts 4 parameters: rows, query, subject, organization. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for open-canada.datasets.search: 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 Apibase. Nothing to install.
open-canada.datasets.search is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the open-canada.datasets.search 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 open-canada.datasets.search. 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.
open-canada.datasets.search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue