get_ontology_layer
Return one ontology layer, its core question, IRI, and primitives.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/get-ontology-layer.md
What get_ontology_layer does on Delx MCP Server
AI agents call get_ontology_layer to retrieve information from Delx MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
layer | string | Yes | Layer id. |
Parameters from the server's own tool schema.
Why get_ontology_layer is rated Low
This tool retrieves and returns ontology metadata (layer information, core question, IRI, primitives). It performs a read-only query operation with no capability to modify, delete, or execute external actions. The blast radius of misuse is minimal—the worst case is information disclosure of the ontology structure itself.
From the tool's definition Tool name 'get_ontology_layer' and description 'Return one ontology layer' indicate a retrieval operation with no modification or side effects. The verb 'Return' confirms data querying without state changes.
Attacks that exploit this kind of access
The rule that runs get_ontology_layer safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_ontology_layer, this is the rule to start with:
get_ontology_layer is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx MCP Server, apply this rule, and every get_ontology_layer call is checked against it from then on.
Questions about get_ontology_layer
Return one ontology layer, its core question, IRI, and primitives. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
get_ontology_layer accepts 1 parameter: layer. Required: layer. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for get_ontology_layer: 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 Delx MCP Server. Nothing to install.
get_ontology_layer 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_ontology_layer 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_ontology_layer. 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_ontology_layer is provided by the Delx MCP Server MCP server (delx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue