Fetch metadata for a specific data catalogue by ID from GitHub. do this before getting the data, if
AI agents call get_catalogue_metadata 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 retrieves metadata about a dataset catalogue without creating, modifying, deleting, or executing any operations. It is a read-only query operation with minimal security risk. The blast radius of misuse is limited to potential information disclosure of publicly available government data catalogue metadata.
From the tool's definition Tool name 'get_catalogue_metadata' and description 'Fetch metadata for a specific data catalogue by ID' indicate data retrieval only.
Documented attack patterns abuse exactly the kind of access get_catalogue_metadata 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_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"get_catalogue_metadata": {}
}
}get_catalogue_metadata 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 metadata for a specific data catalogue by ID from GitHub. do this before getting the data, if. 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_metadata: 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_metadata 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_metadata 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_metadata. 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_metadata 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.