edm_wiki_lint
Health check and trajectory pattern detection for significance wiki. Reports arc distribution, emotional weight stats, recurring themes, and missing fields.
This record as markdown: /tools/deepadata-edm/edm-wiki-lint.md
What edm_wiki_lint does on Deepadata Edm
AI agents call edm_wiki_lint 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 |
|---|---|---|---|
wiki_path | string | Yes | Path to wiki directory |
Parameters from the server's own tool schema.
Why edm_wiki_lint is rated Low
This tool analyzes existing wiki data to provide diagnostic information and statistics. It retrieves and reports on metadata patterns without modifying, creating, or deleting any data. The analysis of recurring themes, missing fields, and emotional weight statistics are all read-only query operations with no side effects.
From the tool's definition Tool performs 'Health check and trajectory pattern detection' and 'Reports' on wiki data. The verbs indicate read-only analysis: checking health, detecting patterns, reporting statistics (arc distribution, emotional weight stats, recurring themes, missing…
Attacks that exploit this kind of access
The rule that runs edm_wiki_lint 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 edm_wiki_lint, this is the rule to start with:
edm_wiki_lint 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 edm_wiki_lint call is checked against it from then on.
Questions about edm_wiki_lint
Health check and trajectory pattern detection for significance wiki. Reports arc distribution, emotional weight stats, recurring themes, and missing fields. It is categorised as a Read tool in the Deepadata Edm MCP Server, which means it retrieves data without modifying state.
edm_wiki_lint accepts 1 parameter: wiki_path. Required: wiki_path. 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 edm_wiki_lint: 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.
edm_wiki_lint 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 edm_wiki_lint 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 edm_wiki_lint. 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.
edm_wiki_lint 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