deepadata_activate_reason
Answer a natural language memory query by reasoning over EDM significance fields (ADR-0018). Classifies the query, retrieves candidate artifacts, and returns a synthesised answer with sources and the significance fields used.
This record as markdown: /tools/deepadata-edm/deepadata-activate-reason.md
What deepadata_activate_reason does on Deepadata Edm
AI agents call deepadata_activate_reason 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 |
|---|---|---|---|
query | string | Yes | Natural language memory query (e.g. "when was I happiest with mum") |
top_k | number | — | Number of sources to return (default: 5, max: 20) |
namespace | string | Yes | Corpus namespace to query (REQUIRED by the platform API, e.g. user-<id>) |
subject_vp_id | string | — | Optional VitaPass subject ID for personalised routing |
Parameters from the server's own tool schema.
Why deepadata_activate_reason is rated Low
The tool classifies queries, retrieves candidate artifacts, and synthesizes answers — all read/query operations with no side effects. It reads EDM significance fields and returns results without modifying any data.
From the tool's definition Answer a natural language memory query by reasoning over EDM significance fields... retrieves candidate artifacts, and returns a synthesised answer with sources
Attacks that exploit this kind of access
The rule that runs deepadata_activate_reason 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 deepadata_activate_reason, this is the rule to start with:
deepadata_activate_reason 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 deepadata_activate_reason call is checked against it from then on.
Questions about deepadata_activate_reason
Answer a natural language memory query by reasoning over EDM significance fields (ADR-0018). Classifies the query, retrieves candidate artifacts, and returns a synthesised answer with sources and the significance fields used. It is categorised as a Read tool in the Deepadata Edm MCP Server, which means it retrieves data without modifying state.
deepadata_activate_reason accepts 4 parameters: query, top_k, namespace, subject_vp_id. Required: query, namespace. 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 deepadata_activate_reason: 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.
deepadata_activate_reason 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 deepadata_activate_reason 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 deepadata_activate_reason. 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.
deepadata_activate_reason 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