validate_ontology_artifact
Check one supplied artifact against the three local Delx Ontology v0.3 shape constraints. No network, private state, or full RDF expansion.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/validate-ontology-artifact.md
What validate_ontology_artifact does on Delx Mcp A2a
AI agents call validate_ontology_artifact to retrieve information from Delx Mcp A2a 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 |
|---|---|---|---|
shapes | array | — | Optional explicit shapes; otherwise inferred from artifact markers. |
artifact | object | Yes | Caller-supplied artifact, at most 32 KiB. Remote JSON-LD contexts are not expanded. |
Parameters from the server's own tool schema.
Why validate_ontology_artifact is rated Low
Even though validate_ontology_artifact only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs validate_ontology_artifact safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For validate_ontology_artifact, this is the rule to start with:
validate_ontology_artifact 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 A2a, apply this rule, and every validate_ontology_artifact call is checked against it from then on.
Questions about validate_ontology_artifact
Check one supplied artifact against the three local Delx Ontology v0.3 shape constraints. No network, private state, or full RDF expansion. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
validate_ontology_artifact accepts 2 parameters: shapes, artifact. Required: artifact. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for validate_ontology_artifact: 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 A2a. Nothing to install.
validate_ontology_artifact 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 validate_ontology_artifact 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 validate_ontology_artifact. 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.
validate_ontology_artifact is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue