validate_edm
Validate an EDM artifact against the v0.8.3 schema and governance rules. Returns validation errors and warnings.
This record as markdown: /tools/deepadata-edm/validate-edm.md
What validate_edm does on Deepadata Edm
AI agents call validate_edm to retrieve information from Deepadata Edm 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 |
|---|---|---|---|
strict | boolean | — | Enable strict validation mode |
artifact | object | Yes | The EDM artifact to validate |
Parameters from the server's own tool schema.
Why validate_edm is rated Low
The tool performs schema validation and checks governance rules, returning diagnostic output (errors and warnings). This is a read-only inspection operation with no side effects on data or systems. No data is created, modified, deleted, executed, or financially affected. The lowest severity applies because misuse by an AI agent would only surface incorrect validation results, not cause damage.
From the tool's definition Tool description states it 'Validate[s] an EDM artifact against the v0.8.3 schema and governance rules. Returns validation errors and warnings.' The verb is 'validate' which performs inspection and returns information without modifying, creating, deleting,…
Attacks that exploit this kind of access
The rule that runs validate_edm safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadata Edm, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For validate_edm, this is the rule to start with:
validate_edm 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 Deepadata Edm, apply this rule, and every validate_edm call is checked against it from then on.
Questions about validate_edm
Validate an EDM artifact against the v0.8.3 schema and governance rules. Returns validation errors and warnings. It is categorised as a Read tool in the Deepadata Edm MCP Server, which means it retrieves data without modifying state.
validate_edm accepts 2 parameters: strict, artifact. Required: artifact. The full parameter table on this page comes from the server's own tool schema.
Register the Deepadata Edm MCP server in PolicyLayer and add a rule for validate_edm: 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 Deepadata Edm. Nothing to install.
validate_edm 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_edm 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_edm. 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_edm is provided by the Deepadata Edm MCP server (deepadata-edm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deepadata Edm, and thousands of servers like it.
This server
Across the catalogue