// SCAN REPORT

Scifinder Route

59 tools. 28 can modify or destroy data without limits.

5 destructive tools with no built-in limits. Policy required.

Last updated: 2 Jul 2026

28 can modify or destroy data

31 read-only

59 tools total

Community server · catalogue entry verified 02/07/2026

How to control Scifinder Route ↓

TOOL MAP

What Scifinder Route exposes to your agents

Read (31) Write / Execute (23) Destructive / Financial (5)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Scifinder Route tools

Destructive · High delete_zotero_mcp_endpoint The tool performs an irreversible deletion operation on configuration data (a Zotero MCP endpoint from a YAML file). Destructive · High empty_trash This tool performs permanent deletion of data that cannot be undone. Destructive · High reparse_document The tool irreversibly clears (deletes) all extracted reactions associated with a document before re-parsing. Destructive · High unlink_reaction_link The tool explicitly removes a link, which is an irreversible deletion of a relationship/association between data records.

28 of Scifinder Route's 59 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Scifinder Route

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

Deny destructive operations

{
  "cleanup_evidence_cache": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

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

Rate limit write operations

{
  "backup_database": {
    "limits": [
      {
        "counter": "backup_database_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "compute_evaluation_metrics": {
    "limits": [
      {
        "counter": "compute_evaluation_metrics_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 Scifinder Route — 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 SCIFINDER ROUTE →

Instant setup, no code required.

FULL CATALOGUE

All 59 Scifinder Route tools

DESTRUCTIVE 5 tools

Destructive cleanup_evidence_cache Clean generated evidence/cache files without deleting source documents. Destructive delete_zotero_mcp_endpoint Delete a Zotero MCP endpoint from the separate Web UI config YAML. Destructive empty_trash Permanently delete all trashed records and their dependent indexes. Destructive reparse_document Clear extracted reactions for a document and parse it again. Destructive unlink_reaction_link Remove an incorrect reaction-level link.

EXECUTE 5 tools

Execute enqueue_literature_linking Start a background Zotero literature linking job for one document or recent reaction steps. Execute rebuild_vector_index Generate embeddings for reaction steps using the configured embedding endpoint. Execute reload_config Reload hot application config from config.yaml without restarting the container. Execute retry_failed_jobs Retry recent failed parse jobs. Execute retry_parse_job Retry a failed or completed parse job by moving it back to the durable queue.

WRITE 18 tools

Write backup_database Create a SQLite database backup, or report Postgres backup guidance. Write confirm_literature_link Confirm a candidate Zotero literature link for a reaction step. Write confirm_reaction_link Confirm a candidate reaction link from PDF evidence block rules. Write export_evaluation_set Export extracted reaction steps as JSONL for manual labeling and regression checks. Write force_reaction_link Manually force link a PDF page to an RDF reaction, overriding confidence rules. Write merge_compounds Merge source compound aliases/reaction links into a target compound. Write recognize_structure_image Send an image region to a configured MolScribe/DECIMER/OSRA-style endpoint and register candidate SMILES. Write record_doi_verification Record DOI source verification performed by an agent or browser workflow. Write register_document Register and parse a local SciFinder export file already visible to the server. Write reject_literature_link Reject an incorrect candidate Zotero literature link. Write restore_trash_item Restore a trashed document, RDF reaction, RDF structure, or reaction step. Write scan_inbox Scan the NAS inbox for supported SciFinder exports and queue/register new files. Write unlink_document_from_batch Remove an incorrectly merged document from an export batch with an audit reason. Write update_config Merge hot-reloadable application config updates into config.yaml and reload them. Write upload_document Copy a server-visible file into the upload area, then register and parse it. Write upload_document_content Upload base64-encoded SciFinder export content through MCP after safety validation. Write upsert_zotero_mcp_endpoint Create or update a Zotero MCP endpoint in the separate Web UI config YAML. Write write_zotero_link_note Optionally create a Zotero note for a confirmed literature link when endpoint writeback is enabled.

READ 31 tools

Read compute_evaluation_metrics Compute regression metrics from a gold-set JSONL file. Read get_chem_status Return RDKit availability and RDF structure index coverage. Read get_compound Return compound metadata, aliases, and linked reactions. Read get_config Return the effective application config. Secrets are masked unless include_secrets is true. Read get_evaluation_status Return the latest evaluation metrics. Read get_export_batch Return one export batch, linked documents, confidence, and merge explanation. Read get_parse_job_status Return parse job status, stage, and error details. Read get_rdf_reaction Return one RDF reaction record with V2000/V3000 molfile structures. Read get_reaction_literature_context Return a reaction step with linked Zotero literature, excerpts, and field differences. Read get_reaction_provenance Return source text/page/parser provenance for a reaction step. Read get_reaction_step Return one structured reaction step. Read get_storage_usage Return NAS data/upload/evidence storage usage. Read get_vector_index_status Return vector index coverage, model, and last error. Read health_check Return server health, configured paths, and indexed object counts. Read list_export_batches List explainable SciFinder export batches linking RDF with readable/visual files. Read list_literature_links List Zotero literature candidates, auto-links, confirmed links, and rejected links. Read list_parse_jobs List recent parse jobs, optionally filtered by status. Read list_rdf_reactions List indexed SciFinder RDF reaction records with scheme/step metadata. Read list_reaction_links List CAS reaction-level evidence links between RDF records and PDF pages. Read list_trash List items in the recycle bin. Read list_zotero_mcp_endpoints List Zotero MCP endpoints from the Web UI hot config plus latest health status. Read search_by_smiles Normalize a SMILES string when RDKit is available, then search compounds. Read search_compounds Search the compound registry by name, CAS, SMILES, or InChIKey. Read search_rdf_structures Search indexed RDF structures by name, CAS, SMILES, or InChIKey. Read search_reaction_steps Search extracted reaction steps by text and structured condition filters. Read semantic_search_reaction_steps Search reaction steps semantically using the configured embedding endpoint. Read similarity_search_structures Run RDKit fingerprint similarity search over indexed RDF compounds. Read substructure_search_structures Run RDKit substructure search over indexed RDF molfile structures. Read test_integration_endpoint Test one configured integration endpoint: llm, embedding, ocr, document_parser, structure_recognition, postgre Read trash_item Move a document, RDF reaction, RDF structure, or reaction step to trash. Read validate_config Validate the current application config and report settings that require container restart.

EXPLORE

Related servers

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

FAQ

Questions about Scifinder Route

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

Yes. The Scifinder Route server exposes 5 destructive tools including cleanup_evidence_cache, delete_zotero_mcp_endpoint, empty_trash. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Scifinder Route? +

The Scifinder Route server has 18 write tools including backup_database, confirm_literature_link, confirm_reaction_link. 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 Scifinder Route.

How many tools does the Scifinder Route MCP server expose? +

59 tools across 4 categories: Destructive, Execute, Read, Write. 31 are read-only. 28 can modify, create, or delete data.

How do I enforce a policy on Scifinder Route? +

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

Deterministic rules across all 59 Scifinder Route tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SCIFINDER ROUTE →

Instant setup, no code required.

59 Scifinder Route tools catalogued and risk-classified — across an index of 43,000+ MCP servers.