Fetch actual data from the data.gov.my API for a specific catalogue.
AI agents call get_catalogue_data to retrieve information from Data Gov My MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval from a public Malaysian government open data catalogue. It has no side effects, does not modify or delete data, does not execute code or commands, and does not involve financial transactions. The sibling tools (get_catalogue_metadata, list_catalogue_ids, search_catalogues) reinforce that this server provides query and discovery capabilities only.
From the tool's definition Tool description states 'Fetch actual data from the data.gov.my API for a specific catalogue' - the verb 'Fetch' and context of retrieving data from an open government data platform indicates read-only data retrieval with no modification, deletion, or…
Documented attack patterns abuse exactly the kind of access get_catalogue_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Data Gov My MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_catalogue_data:
{
"version": "1",
"default": "deny",
"tools": {
"get_catalogue_data": {}
}
}get_catalogue_data 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.
Fetch actual data from the data.gov.my API for a specific catalogue. It is categorised as a Read tool in the Data Gov My MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Data Gov My MCP Server MCP server in PolicyLayer and add a rule for get_catalogue_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 Data Gov My MCP Server. Nothing to install.
get_catalogue_data 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 get_catalogue_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 get_catalogue_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.
get_catalogue_data is provided by the Data Gov My MCP Server MCP server (manfye/data-dosm-mcp-nodejs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Data Gov My 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.
4 Data Gov My MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.