This record as markdown: /tools/20alexl-claude-engram/deps-map.md
What deps_map does on Claude Engram
AI agents call deps_map to retrieve information from Claude Engram without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why deps_map is rated Low
The tool appears to analyze and return information about a file's dependencies or structure. This is a read-only operation with no side effects—it queries data rather than creating, modifying, deleting, or executing code. The low severity reflects minimal blast radius if misused by an agent, as the worst outcome would be exposure of non-sensitive file structure metadata.
From the tool's definition Tool name 'deps_map' and description 'Map a file' indicate a querying/analysis operation that retrieves dependency or structural information about a file without modifying it.
Attacks that exploit this kind of access
The rule that runs deps_map safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Engram, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deps_map, this is the rule to start with:
deps_map 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 Claude Engram, apply this rule, and every deps_map call is checked against it from then on.
Questions about deps_map
Map a file. It is categorised as a Read tool in the Claude Engram MCP Server, which means it retrieves data without modifying state.
Register the Claude Engram MCP server in PolicyLayer and add a rule for deps_map: 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 Claude Engram. Nothing to install.
deps_map 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 deps_map 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 deps_map. 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.
deps_map is provided by the Claude Engram MCP server (20alexl/claude-engram). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Engram, and thousands of servers like it.
This server
Across the catalogue