// SCAN REPORT

Trust Security

9 tools. 4 can modify or destroy data without limits.

4 write tools that can modify data. Rate limits recommended.

Last updated: 29 Jun 2026

4 can modify or destroy data

5 read-only

9 tools total

Community server · catalogue entry verified 29/06/2026

How to control Trust Security ↓

TOOL MAP

What Trust Security exposes to your agents

Read (5) Write / Execute (4) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Trust Security tools

Execute · High scan_and_wait The description is empty, so confidence is lowered. Execute · High scan_repo The tool name 'scan_repo' strongly implies it initiates an active security scan of a repository. Execute · High scan_repo_and_wait The tool name strongly implies it triggers an automated security scan of a repository and waits for results, similar to sibling tools 'scan_repo' and 'scan_and_wait'. Execute · High scan_url Based on the server description, this tool likely triggers an active DAST (Dynamic Application Security Testing) scan against a live URL, which constitutes executing external operations against a target system.

4 of Trust Security's 9 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Trust Security

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

Cap read operations

{
  "analyze_code_security": {
    "limits": [
      {
        "counter": "analyze_code_security_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 Trust Security — 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 TRUST SECURITY →

Instant setup, no code required.

FULL CATALOGUE

All 9 Trust Security tools

EXECUTE 4 tools

Execute scan_and_wait scan_and_wait Execute scan_repo scan_repo Execute scan_repo_and_wait scan_repo_and_wait Execute scan_url scan_url

READ 5 tools

Read analyze_code_security analyze_code_security Read check_secrets check_secrets Read get_fix_plan get_fix_plan Read get_repo_scan_result Get results of a GitHub repo scan by scan ID. Read get_scan_result Get results of a URL scan by scan ID.

FAQ

Questions about Trust Security

Is the Trust Security MCP server safe to use without restrictions? +

The Trust Security server is primarily read-only with 5 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Trust Security MCP server expose? +

9 tools across 1 categories: Read. 5 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Trust Security? +

Register the Trust Security 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 Trust Security tool call.

Deterministic rules across all 9 Trust Security tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON TRUST SECURITY →

Instant setup, no code required.

9 Trust Security tools catalogued and risk-classified — across an index of 43,000+ MCP servers.