# repo_lens_map

Print an ASCII directory tree of a repository so you can find where files live before reading them. Uses the cached .repo-lens/profile.json when present; falls back to a fresh analysis (without writing cache) when missing. Prefer this over listing directories yourself to save tokens.

Agent View of the PolicyLayer registry record for `repo_lens_map`. HTML page: https://policylayer.com/tools/1mper-labs-mcp-server/repo-lens-map

## Facts

- Tool: `repo_lens_map`
- Server: 1mper Labs (`@1mper-labs/mcp-server`) — https://policylayer.com/tools/1mper-labs-mcp-server.md
- Install: `npx -y @1mper-labs/mcp-server`
- Homepage: https://www.npmjs.com/package/@1mper-labs/mcp-server
- Risk category: Write (Medium risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 2
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `dir` | string | no | Directory to map. Defaults to the MCP server process working directory. |
| `maxDepth` | integer | no | Maximum tree depth to render (root is depth 0). Omit for unlimited depth. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "repo_lens_map",
    "arguments": {}
  }
}
```

## Why repo_lens_map is rated Medium

An AI agent can call repo_lens_map faster than any human can review: one bad instruction and it creates or modifies resources in 1mper Labs by the hundred, each call as confident as the last.

Risk signals: Accepts file system path (dir)

## Use case

AI agents use repo_lens_map to create or update resources in 1mper Labs, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 1mper Labs environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 1mper Labs:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "repo_lens_map": {
      "limits": [
        {
          "counter": "repo_lens_map_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on 1mper Labs (2)

- `repo_lens_profile` — Execute — https://policylayer.com/tools/1mper-labs-mcp-server/repo-lens-profile.md
- `repo_lens_analyze` — Read — https://policylayer.com/tools/1mper-labs-mcp-server/repo-lens-analyze.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=1mper-labs-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/1mper-labs-mcp-server
