statcan.series.data
Retrieve the latest N data points for a Statistics Canada time series identified by vector ID. Returns chronological observations with reference period, value, and release timestamp. For annual series: latest_n=10 returns 10 years; for monthly series: 10 returns 10 months. Maximum 100 periods per...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/statcan.series.data.md
What statcan.series.data does on Apibase
AI agents use statcan.series.data 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 |
|---|---|---|---|
latest_n | integer | — | Number of most-recent data points to return (1–100). Defaults to 10. Annual tables: 10 = last 10 years; monthly: 10 = last 10 months. |
vector_id | integer | Yes | Statistics Canada vector ID for the time series to retrieve data for (e.g. 32164132). Obtain from table_metadata or series_info. |
Parameters from the server's own tool schema.
Why statcan.series.data is rated Medium
An AI agent can call statcan.series.data 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 statcan.series.data 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 statcan.series.data, this is the rule to start with:
statcan.series.data 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 statcan.series.data call is checked against it from then on.
Questions about statcan.series.data
Retrieve the latest N data points for a Statistics Canada time series identified by vector ID. Returns chronological observations with reference period, value, and release timestamp. For annual series: latest_n=10 returns 10 years; for monthly series: 10 returns 10 months. Maximum 100 periods per call. Values represent the original unit (e.g. index points, thousands of persons, millions of CAD) with precision set by the series decimals field. Null values indicate suppressed or unavailable data for that period. Source: Statistics Canada WDS, Canada Open Licence, 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.
statcan.series.data accepts 2 parameters: latest_n, vector_id. Required: vector_id. 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 statcan.series.data: 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.
statcan.series.data 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 statcan.series.data 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 statcan.series.data. 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.
statcan.series.data 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