// SCAN REPORT

Geoseo

36 tools. 10 can modify or destroy data without limits.

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

Last updated: 30 Jun 2026

10 can modify or destroy data

26 read-only

36 tools total

Community server · catalogue entry verified 30/06/2026

How to control Geoseo ↓

TOOL MAP

What Geoseo exposes to your agents

Read (26) Write / Execute (10) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Geoseo tools

Execute · Medium openai_query This tool triggers an external operation — querying the OpenAI ChatGPT API with web search enabled. Write · Medium bing_submit_url This tool submits requests to an external search engine system (Bing) to index/crawl a URL, which creates a new request in their system and can affect search rankings and indexing behavior. Write · Medium generate_llms_txt The tool appears to generate or create an llms.txt file, which is used for Generative Engine Optimization (GEO) to communicate with LLMs. Write · Medium gsc_submit_sitemap This tool creates or modifies data in Google Search Console by submitting sitemap metadata.

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

POLICY

How to control Geoseo

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

Rate limit write operations

{
  "bing_submit_url": {
    "limits": [
      {
        "counter": "bing_submit_url_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "aio_check": {
    "limits": [
      {
        "counter": "aio_check_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 Geoseo — 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 GEOSEO →

Instant setup, no code required.

FULL CATALOGUE

All 36 Geoseo tools

EXECUTE 1 tools

Execute openai_query Ask ChatGPT (with web search) a question; return answer + cited URLs.

WRITE 9 tools

Write bing_submit_url Submit a URL for fast crawling. Daily quota applies (default ~10/day). Write generate_llms_txt generate_llms_txt Write gsc_submit_sitemap Submit (or resubmit) a sitemap URL to GSC. Write indexnow_submit_url Notify Bing, Yandex, Naver, Seznam, and Yep that a single URL was published or updated. Write indexnow_submit_urls Batch-notify search engines about up to 10,000 URLs (must share one host). Write snapshot_gsc Run a GSC performance query and persist the rows as a snapshot. Write snapshot_llm_citations Run multi-LLM citation check and persist the per-question results. Write snapshot_serp_aio Run AIO citation check via SerpAPI and persist as serpapi_aio engine rows. Write trend_init Create the local SQLite snapshot DB if it doesn't exist; return its path.

READ 26 tools

Read aio_check Run a Google search via SerpAPI and parse the AI Overview block. Read aio_citation_check aio_citation_check Read audit_page audit_page Read audit_site audit_site Read bing_crawl_issues Crawl errors / blocked URLs / DNS issues reported by Bingbot. Read bing_list_sites List all Bing-verified sites for the API key owner. Read bing_page_stats Per-page stats from Bing Webmaster. Read bing_query_stats Last-6-months query stats from Bing Webmaster (clicks, impressions, position). Read bing_url_info Index status + crawl info for a single URL on Bing. Read claude_query Ask Claude (with server-side web search) a question; return answer + cited URLs. Read gemini_query Ask Gemini (with Google Search grounding) a question; return answer + cited URLs. Read geoseo_status Report which engines are configured and reachable. Read gsc_inspect_url Get index status for a specific URL via the URL Inspection API. Read gsc_list_sites List all Search Console properties the authenticated user can access. Read gsc_performance gsc_performance Read internal_link_graph internal_link_graph Read list_llm_engines Return the LLM engines currently configured (have an API key). Read multi_llm_citation_check multi_llm_citation_check Read multi_llm_query multi_llm_query Read perplexity_citation_check Citation share for target_domain across a Perplexity question batch. Read perplexity_query Ask Perplexity a question; return answer + cited URLs/domains. Read suggest_internal_links suggest_internal_links Read trend_gsc Time-series of clicks/impressions/position from stored GSC snapshots. Read trend_llm_citations Per-snapshot citation share for target_domain over time. Read trend_stats Inventory of what's stored: row counts, sites/domains, oldest/newest snapshots. Read validate_llms_txt Validate an llms.txt file (local path or URL) against the spec.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Geoseo

How do I prevent bulk modifications through Geoseo? +

The Geoseo server has 9 write tools including bing_submit_url, generate_llms_txt, gsc_submit_sitemap. 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 Geoseo.

How many tools does the Geoseo MCP server expose? +

36 tools across 3 categories: Execute, Read, Write. 26 are read-only. 10 can modify, create, or delete data.

How do I enforce a policy on Geoseo? +

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

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

ENFORCE POLICY ON GEOSEO →

Instant setup, no code required.

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