edm_wiki_search
Search significance wiki by emotional criteria. Queries local significance_article.md files by arc_type, emotional_weight, identity_thread.
This record as markdown: /tools/deepadata-edm/edm-wiki-search.md
What edm_wiki_search does on Deepadata Edm
AI agents call edm_wiki_search 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 |
|---|---|---|---|
limit | number | — | Maximum results to return (default: 10) |
arc_type | string | — | Filter by arc type (e.g., grief, transformation, bond) |
wiki_path | string | Yes | Path to wiki directory |
identity_thread | string | — | Search identity threads (substring match) |
recurrence_pattern | string | — | Filter by recurrence pattern |
emotional_weight_min | number | — | Minimum emotional weight (0.0-1.0) |
Parameters from the server's own tool schema.
Why edm_wiki_search is rated Low
This is a read-only search operation that retrieves data from local wiki files based on emotional and thematic criteria. It performs queries without creating, modifying, deleting, or executing any operations. The minimal blast radius of a search tool—returning potentially sensitive wiki content but not altering systems or data—justifies low severity.
From the tool's definition Tool description explicitly states it 'Queries local significance_article.md files' with search parameters (arc_type, emotional_weight, identity_thread). The verb 'Search' and 'Queries' indicate data retrieval with no modification.
Attacks that exploit this kind of access
The rule that runs edm_wiki_search 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_search, this is the rule to start with:
edm_wiki_search 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_search call is checked against it from then on.
Questions about edm_wiki_search
Search significance wiki by emotional criteria. Queries local significance_article.md files by arc_type, emotional_weight, identity_thread. It is categorised as a Read tool in the Deepadata Edm MCP Server, which means it retrieves data without modifying state.
edm_wiki_search accepts 6 parameters: limit, arc_type, wiki_path, identity_thread, recurrence_pattern, emotional_weight_min. 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_search: 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_search 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_search 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_search. 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_search 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