Verify quality issues like missing labels or descriptions. Args: - limit: Maximum results to return (default: 50) - ontologyUri: (optional) Restrict check to resources whose URI starts with this ontology namespace. Use this to avoid false positives from resources imported from other ontologies (e...
AI agents call check_quality 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.
check_quality is a diagnostic/auditing tool that retrieves and reports data quality metrics from the Italian government data catalog. It performs readonly semantic analysis and validation checks without modifying, executing, or deleting any resources. The optional ontologyUri parameter is a query filter to scope results, not an operational parameter. This falls squarely within the Read category.
From the tool's definition Tool description states it 'Verify quality issues like missing labels or descriptions' and 'Returns: List of resources missing rdfs:label or skos:prefLabel'. The arguments (limit, ontologyUri) are filters for inspection/analysis.
Documented attack patterns abuse exactly the kind of access check_quality 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 check_quality:
{
"version": "1",
"default": "deny",
"tools": {
"check_quality": {}
}
}check_quality 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.
Verify quality issues like missing labels or descriptions. Args: - limit: Maximum results to return (default: 50) - ontologyUri: (optional) Restrict check to resources whose URI starts with this ontology namespace. Use this to avoid false positives from resources imported from other ontologies (e.g. core ontology classes referenced as range/domain in the target ontology). Mirrors the URI prefix heuristic used by explore_ontology. Returns: - List of resources missing rdfs:label or skos:prefLabel (checked in both default graph and all named graphs) When to use ontologyUri: - Pass the ontology URI (from list_ontologies) when checking a specific ontology to exclude imported resources. Resources imported from another ontology (e.g. a core class used as range) are NOT a quality issue of the importing ontology — they are defined, with their labels, in the originating ontology. Note: Checks owl:Class, owl:ObjectProperty, owl:DatatypeProperty, and skos:Concept. Label lookup spans both the default graph and all named graphs to avoid false positives caused by label triples residing in a named graph different from where the type assertion was found. False positive filtering: Resources that have only a bare type declaration (a owl:Class with no other properties) are automatically excluded. These are typically import stubs — classes or properties referenced from another module but never developed locally. Only resources with at least one non-type triple are flagged, ensuring the report covers entities that are being actively developed but are missing editorial metadata. 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 check_quality: 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.
check_quality 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 check_quality 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 check_quality. 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.
check_quality 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.