Search for concepts within a specific Controlled Vocabulary (ConceptScheme). Args: - schemeUri: URI of the ConceptScheme (from list_vocabularies) - keyword: Search term for label matching (case-insensitive regex) - limit: Maximum results (default: 20) - lang:
AI agents call search_in_vocabulary to retrieve information from Schema Gov It MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query/search operation that retrieves and matches concepts from a vocabulary without creating, modifying, deleting, or executing any operations. It has no side effects on the data catalog. The parameters (keyword, limit, lang) are all read-only filters. Misuse by an AI agent would only result in unwanted information disclosure or unnecessary API calls, not data corruption or system compromise.
From the tool's definition Tool description states 'Search for concepts within a specific Controlled Vocabulary (ConceptScheme)' with search parameters (keyword, limit, lang). Arguments indicate label matching and result filtering with no modification capabilities.
Documented attack patterns abuse exactly the kind of access search_in_vocabulary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Schema Gov It MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_in_vocabulary:
{
"version": "1",
"default": "deny",
"tools": {
"search_in_vocabulary": {}
}
}search_in_vocabulary 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 concepts within a specific Controlled Vocabulary (ConceptScheme). Args: - schemeUri: URI of the ConceptScheme (from list_vocabularies) - keyword: Search term for label matching (case-insensitive regex) - limit: Maximum results (default: 20) - lang:. It is categorised as a Read tool in the Schema Gov It MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Schema Gov It MCP Server MCP server in PolicyLayer and add a rule for search_in_vocabulary: 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 Schema Gov It MCP Server. Nothing to install.
search_in_vocabulary 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_in_vocabulary 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_in_vocabulary. 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_in_vocabulary is provided by the Schema Gov It MCP Server MCP server (italia/dati-semantic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Schema Gov It 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.
47 Schema Gov It MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.