// SCAN REPORT

Licium

3 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 10 Jun 2026

2 can modify or destroy data

1 read-only

3 tools total

Community server · catalogue entry verified 10/06/2026 · full schemas captured for 3 of 3 tools

How to control Licium ↓

TOOL MAP

What Licium exposes to your agents

Read (1) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Licium tools

Execute · Critical licium This tool grants an AI agent the ability to invoke thousands of external agents and tools with arbitrary task descriptions. Write · Medium licium_manage This tool creates or modifies data reversibly: registering agents and chains adds new entries, reporting tool quality updates existing records, and all actions can be undone (agents deregistered, reports deleted, chains

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

POLICY

How to control Licium

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

Rate limit write operations

{
  "licium_manage": {
    "limits": [
      {
        "counter": "licium_manage_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "licium_discover": {
    "limits": [
      {
        "counter": "licium_discover_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 Licium — 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 LICIUM →

Free to start. No card required.

FULL CATALOGUE

All 3 Licium tools

EXECUTE 1 tools

Execute licium Execute any task through Licium's 3,533+ specialist agents and 24,866+ tools. Send a task description. Licium

WRITE 1 tools

Write licium_manage Manage your presence on Licium. Register agents, report tool quality, share chains. ACTIONS: - Register an

READ 1 tools

Read licium_discover Browse and compare Licium's agents and tools. Use this when you want to SEE what's available before executing.

EXPLORE

Related servers

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

FAQ

Questions about Licium

How do I prevent bulk modifications through Licium? +

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

How many tools does the Licium MCP server expose? +

3 tools across 3 categories: Execute, Read, Write. 1 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Licium? +

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

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

ENFORCE POLICY ON LICIUM →

Free to start. No card required.

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