This query retrieves all entity types in the RDF graph, along with their labels and comments if available. It filters out blank nodes and ensures that only IRI types are returned. The LIMIT clause is set to 100 to restrict the number of entity types returned.
AI agents call sparql_list_entity_types_detailed to retrieve information from Mcp Odbc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval operation querying RDF metadata (entity type definitions, labels, and comments). It has no side effects, does not modify data, does not execute commands, and does not involve financial transactions. The blast radius is minimal—misuse would only expose schema information about entity types in the RDF graph, which is low-risk metadata.
From the tool's definition The tool description explicitly states it 'retrieves all entity types in the RDF graph, along with their labels and comments if available' and 'filters out blank nodes and ensures that only IRI types are returned.' The use of SPARQL LIMIT clause to restrict…
Documented attack patterns abuse exactly the kind of access sparql_list_entity_types_detailed gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Odbc, and nothing reaches the server without passing your rules. This is the rule we recommend for sparql_list_entity_types_detailed:
{
"version": "1",
"default": "deny",
"tools": {
"sparql_list_entity_types_detailed": {}
}
} sparql_list_entity_types_detailed 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.
This query retrieves all entity types in the RDF graph, along with their labels and comments if available. It filters out blank nodes and ensures that only IRI types are returned. The LIMIT clause is set to 100 to restrict the number of entity types returned. It is categorised as a Read tool in the Mcp Odbc MCP Server, which means it retrieves data without modifying state.
Register the Mcp Odbc MCP server in PolicyLayer and add a rule for sparql_list_entity_types_detailed: 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 Mcp Odbc. Nothing to install.
sparql_list_entity_types_detailed 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 sparql_list_entity_types_detailed 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 sparql_list_entity_types_detailed. 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.
sparql_list_entity_types_detailed is provided by the Mcp Odbc MCP server (openlinksoftware/mcp-odbc-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Odbc, 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.
15 Mcp Odbc tools catalogued and risk-classified — across an index of 43,000+ MCP servers.