// SCAN REPORT

Repomend

7 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 3 Jul 2026

1 can modify or destroy data

6 read-only

7 tools total

Community server · catalogue entry verified 03/07/2026

How to control Repomend ↓

TOOL MAP

What Repomend exposes to your agents

Read (6) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Repomend tools

Write · Medium update_finding_status This tool modifies the status of security findings, which is a write operation on metadata.

1 of Repomend's 7 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Repomend

PolicyLayer is an MCP gateway — it sits between your AI agents and Repomend, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "update_finding_status": {
    "limits": [
      {
        "counter": "update_finding_status_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_finding": {
    "limits": [
      {
        "counter": "get_finding_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Repomend — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON REPOMEND →

Instant setup, no code required.

FULL CATALOGUE

All 7 Repomend tools

WRITE 1 tools

Write update_finding_status Update a finding

READ 6 tools

Read get_finding Get full details of a specific finding by ID, including code snippets and remediation guidance Read get_remediation_prompt Get an AI-optimized remediation prompt for a finding. Returns structured markdown with vulnerability details, Read list_findings List security findings for your team, filtered by severity/status/scanner Read list_repos List all monitored repositories for your team Read list_scans List recent scans for your team Read list_targets List all network targets configured for your team

FAQ

Questions about Repomend

How do I prevent bulk modifications through Repomend? +

The Repomend server has 1 write tools including update_finding_status. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Repomend.

How many tools does the Repomend MCP server expose? +

7 tools across 2 categories: Read, Write. 6 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Repomend? +

Register the Repomend MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Repomend tool call.

Deterministic rules across all 7 Repomend tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON REPOMEND →

Instant setup, no code required.

7 Repomend tools catalogued and risk-classified — across an index of 43,000+ MCP servers.