// SCAN REPORT

Y2 Intel

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

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 8 Jul 2026

0 can modify or destroy data

4 read-only

4 tools total

Community server · catalogue entry checked 08/07/2026 · full schemas captured for 4 of 4 tools

How to control Y2 Intel ↓

TOOL MAP

What Y2 Intel exposes to your agents

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

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Y2 Intel costs in tokens

407 tokens of tool definitions, loaded on every request

0.2% of a 200k context window

127 heaviest tool: y2_list_news

Full per-tool breakdown → Model it in the token calculator →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Y2 Intel

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

Cap read operations

{
  "y2_get_openapi_operation": {
    "limits": [
      {
        "counter": "y2_get_openapi_operation_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 Y2 Intel — 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 Y2 INTEL →

Instant setup, no code required.

FULL CATALOGUE

All 4 Y2 Intel tools

READ 4 tools

Read y2_get_openapi_operation Return one Y2 OpenAPI operation by operationId or path plus method. Does not require Y2_API_KEY. Read y2_get_report Get one Y2 report by ID. Requires reports:read. Read y2_list_news List bounded Y2 News Terminal items. Requires news:read. Read y2_list_reports List recent Y2 reports. Requires reports:read.

FAQ

Questions about Y2 Intel

Is the Y2 Intel MCP server safe to use without restrictions? +

The Y2 Intel server is primarily read-only with 4 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 Y2 Intel MCP server expose? +

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

How do I enforce a policy on Y2 Intel? +

Register the Y2 Intel 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 Y2 Intel tool call.

Deterministic rules across all 4 Y2 Intel tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON Y2 INTEL →

Instant setup, no code required.

4 Y2 Intel tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Y2 Intel's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →