# repo_lens_profile

Return the cached .repo-lens/profile.json for a repository as JSON. Use this when you specifically need the previously generated machine-readable profile (schemaVersion, languages, manifests, tree). If no cache exists, the result tells you to run repo_lens_analyze first. This tool never writes anything.

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

## Facts

- Tool: `repo_lens_profile`
- 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: Execute (High risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `dir` | string | no | Directory whose cached profile to load. Defaults to the MCP server process working directory. |

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_profile",
    "arguments": {}
  }
}
```

## Why repo_lens_profile is rated High

repo_lens_profile triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signals: Accepts file system path (dir)

## Use case

AI agents invoke repo_lens_profile to trigger actions in 1mper Labs. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## 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_profile": {
      "limits": [
        {
          "counter": "repo_lens_profile_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on 1mper Labs (2)

- `repo_lens_analyze` — Read — https://policylayer.com/tools/1mper-labs-mcp-server/repo-lens-analyze.md
- `repo_lens_map` — Write — https://policylayer.com/tools/1mper-labs-mcp-server/repo-lens-map.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
