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 an...
This record as markdown: /tools/1mper-labs-mcp-server/repo-lens-profile.md
What repo_lens_profile does on 1mper Labs
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
dir | string | — | Directory whose cached profile to load. Defaults to the MCP server process working directory. |
Parameters from the server's own tool schema.
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 signalsAccepts file system path (dir)
Attacks that exploit this kind of access
The rule that runs repo_lens_profile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1mper Labs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For repo_lens_profile, this is the rule to start with:
repo_lens_profile stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 1mper Labs, apply this rule, and every repo_lens_profile call is checked against it from then on.
Questions about 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. It is categorised as a Execute tool in the 1mper Labs MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
repo_lens_profile accepts 1 parameter: dir. The full parameter table on this page comes from the server's own tool schema.
Register the 1mper Labs MCP server in PolicyLayer and add a rule for repo_lens_profile: 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 1mper Labs. Nothing to install.
repo_lens_profile is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the repo_lens_profile 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 repo_lens_profile. 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.
repo_lens_profile is provided by the 1mper Labs MCP server (@1mper-labs/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1mper Labs, and thousands of servers like it.
Across the catalogue