// SCAN REPORT

TensorFeed

42 tools. 6 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 6 May 2026

6 can modify or destroy data

36 read-only

42 tools total

// TOOL MAP

Read (36) Write / Execute (5) Destructive / Financial (1)

// WHAT CAN GO WRONG

Destructive tools (delete_watch) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (create_digest_watch, create_leaderboard_rank_watch, create_price_watch) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (whats_new) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

// RECOMMENDED RULES

Deny destructive operations

delete_watch:
  rules:
    - action: deny

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

create_digest_watch:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

benchmark_series:
  rules:
    - rate_limit: 60/minute

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

// ALL 42 TENSORFEED TOOLS

DESTRUCTIVE 1 tools

Destructive delete_watch

EXECUTE 1 tools

Execute whats_new

WRITE 4 tools

Write create_digest_watch Write create_leaderboard_rank_watch Write create_price_watch Write create_status_watch

READ 36 tools

Read benchmark_series Read benchmark_series_free Read compare_models Read cost_projection Read get_account_balance Read get_account_usage Read get_agent_activity Read get_ai_ecosystem_today Read get_ai_news Read get_ai_papers_trending Read get_ai_status Read get_ai_today Read get_arxiv_recent Read get_hf_daily_papers Read get_hf_trending Read get_hot_issues Read get_model_deprecations Read get_model_pricing Read get_openrouter_models Read get_reddit_trending Read is_service_down Read list_watches Read mcp_registry_series Read mcp_registry_snapshot Read news_search Read premium_agents_directory Read premium_routing Read pricing_series Read pricing_series_free Read probe_latest Read probe_series Read provider_deepdive Read status_leaderboard Read status_leaderboard_free Read status_uptime Read status_uptime_free

// FAQ

Can an AI agent delete data through the TensorFeed MCP server? +

Yes. The TensorFeed server exposes 1 destructive tools including delete_watch. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through TensorFeed? +

The TensorFeed server has 4 write tools including create_digest_watch, create_leaderboard_rank_watch, create_price_watch. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the TensorFeed MCP server expose? +

42 tools across 4 categories: Destructive, Execute, Read, Write. 36 are read-only. 6 can modify, create, or delete data.

How do I add Intercept to my TensorFeed setup? +

One line change. Instead of running the TensorFeed server directly, prefix it with Intercept: intercept -c tensorfeed.yaml -- npx -y @@tensorfeed/mcp-server. Download a pre-built policy from policylayer.com/policies/tensorfeed and adjust the limits to match your use case.

// RELATED SERVERS

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

TensorFeed

Other MCP servers with similar tools.

Let agents act without letting them run wild.