Low Risk

list_structure

แสดงโครงสร้างพระไตรปิฎกทั้ง 3 ปิฎก พร้อมสถิติ coverage 💡 ใช้ tool นี้เมื่อ: - User ถามภาพรวมพระไตรปิฎก (มีอะไรบ้าง / นิกายอะไร) - ตรวจ coverage ก่อนสัญญาว่าจะค้นได้ — ดู segment_count > 0 เป็นตัว ตัดสินว่า sub-collection นั้นโหลดแล้ว - Verify scope สำหรับการ compile artifact 📊 State ปัจจุบัน v1...

Part of the Tripitaka MCP server.

list_structure is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE TRIPITAKA MCP →

Free to start. No card required.

AI agents call list_structure to retrieve information from Tripitaka MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though list_structure only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_structure": {}
  }
}

See the full Tripitaka MCP policy for all 10 tools.

Get this rule live on your own Tripitaka MCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TRIPITAKA MCP →

View all 10 tools →

These attack patterns abuse exactly the kind of access list_structure gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so list_structure only ever does what you allow.

SECURE TRIPITAKA MCP →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the list_structure tool do? +

แสดงโครงสร้างพระไตรปิฎกทั้ง 3 ปิฎก พร้อมสถิติ coverage 💡 ใช้ tool นี้เมื่อ: - User ถามภาพรวมพระไตรปิฎก (มีอะไรบ้าง / นิกายอะไร) - ตรวจ coverage ก่อนสัญญาว่าจะค้นได้ — ดู segment_count > 0 เป็นตัว ตัดสินว่า sub-collection นั้นโหลดแล้ว - Verify scope สำหรับการ compile artifact 📊 State ปัจจุบัน v1.1+ (เทียบเท่า SuttaCentral bilara-data): - Sutta Piṭaka ครบ: DN 37, MN 155, SN 1,829, AN 1,419, KN 2,351 sections (~284,702 segments รวม) — Pāli + Sujato EN - Vinaya Piṭaka ครบ: Bhikkhu Vibhaṅga 222, Bhikkhunī Vibhaṅga 127, Khandhaka 22, Parivāra 51 + Pātimokkha 2 (~71,557 segs) — Pāli + Brahmali EN - Abhidhamma Piṭaka ครบ: 7 books (ds, vb, dt, pp, kv, ya, patthana) ~88,414 segs — Pāli only (bilara ไม่มี EN ทุก translator) - รวม ~444,673 segments ใน DB ⚠️ Quirks ที่ยังอยู่: - Schema มี duplicate codes legacy + SC modern ใช้ co-exist: - Vinaya: vin-v/vin-m/vin-c/vin-p (legacy, segment_count = 0) คู่กับ pli-tv-bu-vb/pli-tv-bi-vb/pli-tv-kd/pli-tv-pvr (active, มี segments) - Abhidhamma: ym/pt (legacy = 0) คู่กับ ya/patthana (active) - เลือก code ที่ segment_count > 0 ตอนใช้งาน — ตัวอื่นเป็น metadata placeholder จาก migration เก่า 🌐 ภาษา: ส่งกลับ Pāli + Thai + English labels เสมอ (metadata ไม่ใช่ segment text); text content ตามภาษาที่ ENABLED_LANGUAGES บอก. ตอนนี้ ฉบับแปลไทยใน DB ยังไม่มี — Thai user ใช้ cross_reference 84000.org เพิ่ม Returns: โครงสร้างแบบ hierarchical: - pitakas{vinaya/sutta/abhidhamma} → nikayas[] - แต่ละ nikaya: code, name (3 ภาษา), sutta_count, segment_count. It is categorised as a Read tool in the Tripitaka MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_structure? +

Register the Tripitaka MCP server in PolicyLayer and add a rule for list_structure: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Tripitaka MCP. Nothing to install.

What risk level is list_structure? +

list_structure is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_structure? +

Yes. Add a rate_limit block to the list_structure rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block list_structure completely? +

Set action: deny in the PolicyLayer policy for list_structure. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides list_structure? +

list_structure is provided by the Tripitaka MCP server (https://mcp.tripitaka-mcp.com/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Tripitaka MCP tool call.

Deterministic rules across all 10 Tripitaka MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.