Philosophy

20 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated:

1 can modify or destroy data
19 read-only
20 tools total

Community server · catalogue entry verified 04/07/2026

How to control Philosophy ↓

What Philosophy exposes to your agents

Read (19) Write / Execute (1) Destructive / Financial (0)
High Risk

The most dangerous Philosophy tools

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

How to control Philosophy

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

Rate limit write operations
{
  "fetch_pdf": {
    "limits": [
      {
        "counter": "fetch_pdf_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "fetch_text": {
    "limits": [
      {
        "counter": "fetch_text_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

  1. Create a free account and register Philosophy — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON PHILOSOPHY →

Instant setup, no code required.

All 20 Philosophy tools

READ 19 tools
Read fetch_text Fetch any URL and return its readable text — the catch-all for sources without a Read get_archive_text Fetch the OCR full text of an Internet Archive item by identifier (from Read get_fulltext Download a PhilArchive record Read get_gutenberg_text Fetch the plain-text body of a Project Gutenberg book by numeric id (from search_gutenberg). Read get_paper Fetch canonical metadata for one PhilArchive/PhilPapers record via OAI-PMH. Read get_sep_entry Fetch the text of a SEP entry. Accepts a slug (e.g. Read get_wikisource_text Fetch the plain text of a Wikisource page by title (from search_wikisource). Returns one Read list_recent List recently added/updated PhilArchive records in a date window, via OAI-PMH Read local_doc_info Open a local PDF or plain-text file and return a cheap overview — page count, Read local_doc_read Read a bounded slice of a local PDF or text file — a page range starting at page_from — and Read local_doc_search Search a local PDF or text file for a keyword or regular expression and return only the Read research One-shot literature scan: runs a keyword search across PhilPapers/PhilArchive and, for Read search_doab Search the Directory of Open Access Books — peer-reviewed, fully open-access academic Read search_gutenberg Search Project Gutenberg for public-domain classics and out-of-copyright translations Read search_internet_archive Search the Internet Archive for scanned, out-of-print monographs, journals, and Read search_openlibrary Search Open Library for books — strong for modern editions and translations as metadata, Read search_papers Keyword search across PhilPapers / PhilArchive (philosophy preprints and published Read search_sep Search SEP (the standard scholarly reference) by matching its full entry index. Read search_wikisource Search Wikisource for primary texts and translations (en, de, ko, ...).

Questions about Philosophy

How do I prevent bulk modifications through Philosophy? +

The Philosophy server has 1 write tools including fetch_pdf. 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 Philosophy.

How many tools does the Philosophy MCP server expose? +

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

How do I enforce a policy on Philosophy? +

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

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

Instant setup, no code required.

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.