edm_project
Project an EDM artifact into the canonical agent-consumable shape (ADR-0009). Returns governance-preserving projection with optional LLM-generated context note.
This record as markdown: /tools/deepadata-edm/edm-project.md
What edm_project does on Deepadata Edm
AI agents call edm_project 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 |
|---|---|---|---|
artifact_id | string | Yes | The artifact ID to project |
context_note | boolean | — | Generate a 2-3 sentence LLM summary for context injection (default: false) |
Parameters from the server's own tool schema.
Why edm_project is rated Low
This tool retrieves and transforms EDM artifacts for consumption by agents without modifying the underlying data or causing side effects. The projection operation is a read-like transformation that reshapes existing data into a different format. No create, delete, execute, or financial operations are described.
From the tool's definition Tool description states it 'Project[s] an EDM artifact into the canonical agent-consumable shape' and 'Returns governance-preserving projection with optional LLM-generated context note.' The verbs 'project' and 'returns' indicate data retrieval and…
Attacks that exploit this kind of access
The rule that runs edm_project 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_project, this is the rule to start with:
edm_project 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_project call is checked against it from then on.
Questions about edm_project
Project an EDM artifact into the canonical agent-consumable shape (ADR-0009). Returns governance-preserving projection with optional LLM-generated context note. It is categorised as a Read tool in the Deepadata Edm MCP Server, which means it retrieves data without modifying state.
edm_project accepts 2 parameters: artifact_id, context_note. Required: artifact_id. 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_project: 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_project 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_project 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_project. 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_project 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