open-canada.reference.subject_list
List the Government of Canada open data subject taxonomy (e.g. "health_and_safety", "nature_and_environment") with the current dataset count per subject, optionally filtered by a substring. Use the returned subject slug as the subject filter for open-canada.dataset_search. Data: open.canada.ca CK...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/open-canada.reference.subject-list.md
What open-canada.reference.subject_list does on Apibase
AI agents use open-canada.reference.subject_list 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 |
|---|---|---|---|
query | string | — | Substring filter on subject slug (e.g. "health") |
Parameters from the server's own tool schema.
Why open-canada.reference.subject_list is rated Medium
An AI agent can call open-canada.reference.subject_list 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.reference.subject_list 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.reference.subject_list, this is the rule to start with:
open-canada.reference.subject_list 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.reference.subject_list call is checked against it from then on.
Questions about open-canada.reference.subject_list
List the Government of Canada open data subject taxonomy (e.g. "health_and_safety", "nature_and_environment") with the current dataset count per subject, optionally filtered by a substring. Use the returned subject slug as the subject filter for open-canada.dataset_search. 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.reference.subject_list accepts 1 parameter: query. 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.reference.subject_list: 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.reference.subject_list 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.reference.subject_list 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.reference.subject_list. 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.reference.subject_list 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