edm_wiki_generate
Generate significance wiki from source text. Extracts EDM artifact and produces wiki_article.md + significance_article.md. Requires DEEPADATA_API_KEY for extraction.
This record as markdown: /tools/deepadata-edm/edm-wiki-generate.md
What edm_wiki_generate does on Deepadata Edm
AI agents use edm_wiki_generate to create or update resources in Deepadata Edm, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Deepadata Edm environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
profile | string | — | Extraction profile (default: extended) |
output_dir | string | — | Output directory for wiki files (default: ./wiki) |
source_path | string | Yes | Path to source file or directory containing .txt/.md files |
Parameters from the server's own tool schema.
Why edm_wiki_generate is rated Medium
This tool creates new wiki articles from source text. While it doesn't execute arbitrary code or irreversibly destroy data, it does create or write new content artifacts (wiki_article.md and significance_article.md). This is a Write operation.
From the tool's definition Tool description states it 'produces wiki_article.md + significance_article.md', indicating creation of new files/content. The term 'generates' and 'produces' confirm data creation rather than retrieval or modification of existing content.
Risk signalsAccepts file system path (source_path)
Attacks that exploit this kind of access
The rule that runs edm_wiki_generate 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_generate, this is the rule to start with:
edm_wiki_generate stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_generate call is checked against it from then on.
Questions about edm_wiki_generate
Generate significance wiki from source text. Extracts EDM artifact and produces wiki_article.md + significance_article.md. Requires DEEPADATA_API_KEY for extraction. It is categorised as a Write tool in the Deepadata Edm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
edm_wiki_generate accepts 3 parameters: profile, output_dir, source_path. Required: source_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_generate: 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_generate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the edm_wiki_generate 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_generate. 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_generate 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