// SCAN REPORT

Cross-Project MCP Server

9 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

8 read-only

9 tools total

Community server · catalogue entry verified 03/07/2026

How to control Cross-Project MCP Server ↓

TOOL MAP

What Cross-Project MCP Server exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Cross-Project MCP Server tools

Write · Medium submit_task This tool creates new task entries and delegates work, which are reversible write operations.

1 of Cross-Project MCP Server'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 Cross-Project MCP Server

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

Rate limit write operations

{
  "submit_task": {
    "limits": [
      {
        "counter": "submit_task_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "find_files": {
    "limits": [
      {
        "counter": "find_files_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 Cross-Project MCP Server — 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 CROSS-PROJECT →

Instant setup, no code required.

FULL CATALOGUE

All 9 Cross-Project MCP Server tools

WRITE 1 tools

Write submit_task DELEGATE work to this repository

READ 8 tools

Read find_files Find files by name pattern in the source project at: ${resolvedSourcePath}. Supports glob patterns like Read get_agent_instructions Get the agent Read get_file_outline Get a structural outline of a source file from: ${resolvedSourcePath}. Extracts function names, class definiti Read list_directory List files and directories in the source project at: ${resolvedSourcePath}. Returns names, types (file/directo Read list_tasks List tasks in the project Read read_file Read the contents of a file from the source project at: ${resolvedSourcePath}. Returns the file content as tex Read read_task Read the full content of a specific task file. Read search_code Search for patterns across the source project at: ${resolvedSourcePath}. Supports both literal text and regex

FAQ

Questions about Cross-Project MCP Server

How do I prevent bulk modifications through Cross-Project MCP Server? +

The Cross-Project MCP Server server has 1 write tools including submit_task. 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 Cross-Project MCP Server.

How many tools does the Cross-Project MCP Server MCP server expose? +

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

How do I enforce a policy on Cross-Project MCP Server? +

Register the Cross-Project MCP Server 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 Cross-Project MCP Server tool call.

Deterministic rules across all 9 Cross-Project MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CROSS-PROJECT →

Instant setup, no code required.

9 Cross-Project MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.