Low Risk

opendosm_get_dataset

Fetch records from an official Malaysian statistics dataset (data.gov.my / OpenDOSM, Dept of Statistics Malaysia). Keyless, authoritative. The dataset id is REQUIRED — there is no listing endpoint, so use opendosm_list_datasets or opendosm_dataset_meta to discover ids and their columns. Verified ...

Part of the Opendosm My server.

opendosm_get_dataset is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE OPENDOSM MY →

Free to start. No card required.

AI agents call opendosm_get_dataset to retrieve information from Opendosm My without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though opendosm_get_dataset only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "opendosm_get_dataset": {}
  }
}

See the full Opendosm My policy for all 23 tools.

Get this rule live on your own Opendosm My server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY OPENDOSM MY →

View all 23 tools →

These attack patterns abuse exactly the kind of access opendosm_get_dataset gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so opendosm_get_dataset only ever does what you allow.

SECURE OPENDOSM MY →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the opendosm_get_dataset tool do? +

Fetch records from an official Malaysian statistics dataset (data.gov.my / OpenDOSM, Dept of Statistics Malaysia). Keyless, authoritative. The dataset id is REQUIRED — there is no listing endpoint, so use opendosm_list_datasets or opendosm_dataset_meta to discover ids and their columns. Verified high-value ids: cpi_headline (Headline Consumer Price Index, monthly (1980–present).); cpi_core (Core CPI (excludes volatile items), monthly.); gdp_qtr_real (Real GDP, quarterly (constant 2015 prices).); economic_indicators (Leading / coincident / lagging economic indicator indices, monthly.); ipi (Industrial Production Index, monthly (seasonally adjusted + absolute).); lfs_month (Labour force survey, monthly: unemployment rate, participation rate, employment.); fuelprice (Weekly retail fuel prices (RON95, RON97, diesel) in MYR per litre.); hh_income (Household income: mean and median (MYR), by survey year.); population_malaysia (Malaysia population by age / sex / ethnicity (thousands), annual.); population_state (Population by state, age, sex, ethnicity (thousands).); births (Live births by state and date.); deaths (Deaths: absolute count and crude rate, annual.). Filter syntax is value@column (e.g. filter="overall@division" keeps only rows where division=overall). Range syntax is column[start:end] on NUMERIC columns only, either bound optional (e.g. range="index[130:140]", range="index[135:]"). Date ranges are NOT supported by range; instead use sort="-date" with limit to get the most recent rows. sort="-col" is descending, sort="col" ascending.. It is categorised as a Read tool in the Opendosm My MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on opendosm_get_dataset? +

Register the Opendosm My MCP server in PolicyLayer and add a rule for opendosm_get_dataset: 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 Opendosm My. Nothing to install.

What risk level is opendosm_get_dataset? +

opendosm_get_dataset is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit opendosm_get_dataset? +

Yes. Add a rate_limit block to the opendosm_get_dataset 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.

How do I block opendosm_get_dataset completely? +

Set action: deny in the PolicyLayer policy for opendosm_get_dataset. 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.

What MCP server provides opendosm_get_dataset? +

opendosm_get_dataset is provided by the Opendosm My MCP server (https://gateway.pipeworx.io/opendosm-my/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Opendosm My tool call.

Deterministic rules across all 23 Opendosm My tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.