Search for catalogues by keyword in their names or descriptions.
AI agents call search_catalogues 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 information from a government data catalogue without side effects. It does not create, modify, delete, or execute any operations—it only searches and returns results. This is a classic Read category tool with minimal risk.
From the tool's definition Tool performs a search operation on catalogue names and descriptions to retrieve matching results. The verb "search" and the read-only nature of querying metadata indicate no data modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access search_catalogues 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 search_catalogues:
{
"version": "1",
"default": "deny",
"tools": {
"search_catalogues": {}
}
} search_catalogues 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.
Search for catalogues by keyword in their names or descriptions. 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 search_catalogues: 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.
search_catalogues 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 search_catalogues 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 search_catalogues. 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.
search_catalogues 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.