# tcm_ctd_gene_interactions

A read tool on the OpenTCM_Discovery MCP server.

Agent View of the PolicyLayer registry record for `tcm_ctd_gene_interactions`. HTML page: https://policylayer.com/tools/opentcm-discovery/tcm-ctd-gene-interactions

## Facts

- Tool: `tcm_ctd_gene_interactions`
- Server: OpenTCM_Discovery (`S0mbraD/OpenTCM_Discovery`) — https://policylayer.com/tools/opentcm-discovery.md
- Homepage: https://github.com/S0mbraD/OpenTCM_Discovery
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "tcm_ctd_gene_interactions",
    "arguments": {}
  }
}
```

## Why tcm_ctd_gene_interactions is rated Low

Tool queries gene interactions in TCM research database; no modification, execution, or financial operations evident.

From the tool's own definition: "uninformative description; sibling tools indicate research/discovery context"

## Use case

AI agents call tcm_ctd_gene_interactions to retrieve information from OpenTCM_Discovery without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches OpenTCM_Discovery:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "tcm_ctd_gene_interactions": {}
  }
}
```

## Other tools on OpenTCM_Discovery (68)

- `dock_batch_screening` — Execute — https://policylayer.com/tools/opentcm-discovery/dock-batch-screening.md
- `dock_geometric_ppi` — Execute — https://policylayer.com/tools/opentcm-discovery/dock-geometric-ppi.md
- `dock_rescore` — Execute — https://policylayer.com/tools/opentcm-discovery/dock-rescore.md
- `dock_vina_docking` — Execute — https://policylayer.com/tools/opentcm-discovery/dock-vina-docking.md
- `tcm_multi_path_run` — Execute — https://policylayer.com/tools/opentcm-discovery/tcm-multi-path-run.md
- `tcm_smart_run` — Execute — https://policylayer.com/tools/opentcm-discovery/tcm-smart-run.md
- `dock_analyze_contacts` — Read — https://policylayer.com/tools/opentcm-discovery/dock-analyze-contacts.md
- `dock_analyze_runtime` — Read — https://policylayer.com/tools/opentcm-discovery/dock-analyze-runtime.md
- `dock_check_environment` — Read — https://policylayer.com/tools/opentcm-discovery/dock-check-environment.md
- `dock_compare_experiments` — Read — https://policylayer.com/tools/opentcm-discovery/dock-compare-experiments.md
- `dock_fetch_structure` — Read — https://policylayer.com/tools/opentcm-discovery/dock-fetch-structure.md
- `dock_report_insight` — Read — https://policylayer.com/tools/opentcm-discovery/dock-report-insight.md
- `tcm_adme_profile` — Read — https://policylayer.com/tools/opentcm-discovery/tcm-adme-profile.md
- `tcm_admet_predict` — Read — https://policylayer.com/tools/opentcm-discovery/tcm-admet-predict.md
- `tcm_align_tcmsp` — Read — https://policylayer.com/tools/opentcm-discovery/tcm-align-tcmsp.md
- `tcm_analysis_topology` — Read — https://policylayer.com/tools/opentcm-discovery/tcm-analysis-topology.md
- `tcm_analyze_runtime` — Read — https://policylayer.com/tools/opentcm-discovery/tcm-analyze-runtime.md
- `tcm_audit_evidence` — Read — https://policylayer.com/tools/opentcm-discovery/tcm-audit-evidence.md
- `tcm_broad_names` — Read — https://policylayer.com/tools/opentcm-discovery/tcm-broad-names.md
- `tcm_cache_status` — Read — https://policylayer.com/tools/opentcm-discovery/tcm-cache-status.md
- `tcm_check_database_status` — Read — https://policylayer.com/tools/opentcm-discovery/tcm-check-database-status.md
- `tcm_check_docking_replay` — Read — https://policylayer.com/tools/opentcm-discovery/tcm-check-docking-replay.md
- `tcm_chembl_lookup` — Read — https://policylayer.com/tools/opentcm-discovery/tcm-chembl-lookup.md
- `tcm_classify_structure` — Read — https://policylayer.com/tools/opentcm-discovery/tcm-classify-structure.md
- `tcm_clean_table` — Read — https://policylayer.com/tools/opentcm-discovery/tcm-clean-table.md
- `tcm_cross_database_screen` — Read — https://policylayer.com/tools/opentcm-discovery/tcm-cross-database-screen.md
- `tcm_dependency_status` — Read — https://policylayer.com/tools/opentcm-discovery/tcm-dependency-status.md
- `tcm_dgidb_interactions` — Read — https://policylayer.com/tools/opentcm-discovery/tcm-dgidb-interactions.md
- `tcm_enrichment_analysis` — Read — https://policylayer.com/tools/opentcm-discovery/tcm-enrichment-analysis.md
- `tcm_ensembl_lookup` — Read — https://policylayer.com/tools/opentcm-discovery/tcm-ensembl-lookup.md
- …and 38 more: https://policylayer.com/tools/opentcm-discovery.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=opentcm-discovery · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/opentcm-discovery
