Skip to content

io.tooloracle/tlpt

by tooloracle.io · remote · no sign-in to list tools · v1.0.0 · published by io.tooloracle

TLPTOracle — 17-tool TIBER-EU TLPT framework: scope, threat intel, scenarios, reports.

Changes · 15
CompareRegistry entry

17 tools: 15 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http tlpt https://tooloracle.io/tlpt/mcp/

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

17 tools

Changes things 15Claude Code: ask
  • attack_chainGenerate kill chain for a TIBER-EU scenario with MITRE mapping.No findings

    Why it is in this group

    • The description's first verb is "generate": a word for a change.
    Description, as the server wrote it
    Generate kill chain for a TIBER-EU scenario with MITRE mapping.
  • auto_simulateAutonomous TLPT simulation: generates TIBER-EU scenarios, maps MITRE ATT&CK, creates findings, rates detection.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Autonomous TLPT simulation: generates TIBER-EU scenarios, maps MITRE ATT&CK, creates findings, rates detection. Art. 26.
  • evidence_bundleCompile TLPT evidence for authority attestation.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Compile TLPT evidence for authority attestation.
  • generate_scenariosList all 8 TIBER-EU scenarios available for autonomous simulation.No findings

    Why it is in this group

    • The name "generate_scenarios" says "generate": a word for a change.
    Description, as the server wrote it
    List all 8 TIBER-EU scenarios available for autonomous simulation.
  • health_checkServer status.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Server status.
  • mitre_mapMap MITRE ATT&CK techniques to DORA TLPT.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Map MITRE ATT&CK techniques to DORA TLPT. Filter by technique ID or tactic.
  • obligation_mapTLPT obligations DORA-TST-06 to TST-10.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    TLPT obligations DORA-TST-06 to TST-10.
  • phase_trackerTrack TIBER-EU 8-phase lifecycle.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Track TIBER-EU 8-phase lifecycle.
  • register_exerciseRegister a TLPT/pentest exercise.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Register a TLPT/pentest exercise.
  • remediation_planTrack remediation of TLPT findings.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Track remediation of TLPT findings. Set add=true to create.
  • sync_to_ampelPush TLPT results to AmpelOracle Art.No findings

    Why it is in this group

    • The name "sync_to_ampel" says "sync": a word for a change.
    Description, as the server wrote it
    Push TLPT results to AmpelOracle Art. 26 checks.
  • team_assignmentManage Red/Blue/White/Purple team assignments.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Manage Red/Blue/White/Purple team assignments.
  • test_calendarAnnual testing schedule and compliance check.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Annual testing schedule and compliance check.
  • threat_profileDefine threat landscape for TLPT scoping.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Define threat landscape for TLPT scoping.
  • tlpt_readinessAssess organizational readiness for a TLPT exercise.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Assess organizational readiness for a TLPT exercise.
Only reads 2Claude Code: allow
  • finding_registerLog a pentest/TLPT finding.No findings

    Why it is in this group

    • The description's first verb is "log": a word for reading.
    Description, as the server wrote it
    Log a pentest/TLPT finding.
  • pingConnectivity test.No findings

    Why it is in this group

    • The name "ping" says "ping": a word for reading.
    Description, as the server wrote it
    Connectivity test.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http tlpt https://tooloracle.io/tlpt/mcp/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__tlpt__finding_register",
      "mcp__tlpt__ping"
    ],
    "ask": [
      "mcp__tlpt__register_exercise",
      "mcp__tlpt__phase_tracker",
      "mcp__tlpt__threat_profile",
      "mcp__tlpt__team_assignment",
      "mcp__tlpt__remediation_plan",
      "mcp__tlpt__evidence_bundle",
      "mcp__tlpt__test_calendar",
      "mcp__tlpt__tlpt_readiness",
      "mcp__tlpt__health_check",
      "mcp__tlpt__auto_simulate",
      "mcp__tlpt__mitre_map",
      "mcp__tlpt__attack_chain",
      "mcp__tlpt__generate_scenarios",
      "mcp__tlpt__sync_to_ampel",
      "mcp__tlpt__obligation_map"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tlpt. Review it before you use it.