GLPI MCP

40 tools. 17 can modify or destroy data without limits.

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

Last updated:

17 can modify or destroy data
23 read-only
40 tools total

Community server · catalogue entry verified 29/06/2026

How to control GLPI MCP ↓

What GLPI MCP exposes to your agents

Read (23) Write / Execute (15) Destructive / Financial (2)
Critical Risk

The most dangerous GLPI MCP tools

17 of GLPI MCP's 40 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control GLPI MCP

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

Deny destructive operations
{
  "delete_task": {
    "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
{
  "add_followup": {
    "limits": [
      {
        "counter": "add_followup_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "get_followup": {
    "limits": [
      {
        "counter": "get_followup_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register GLPI MCP — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON GLPI →

Instant setup, no code required.

All 40 GLPI MCP tools

READ 23 tools
Read get_followup Retourne le détail d'un suivi spécifique. Read get_groups Liste les groupes GLPI. Read get_kb_article Retourne le detail complet d'un article de la base de connaissances. Read get_kb_article_visibility Retourne les regles de visibilite d'un article KB : Read get_solution Retourne la solution d'un ticket. Read get_ticket Retourne le détail complet d'un ticket, avec libellés lisibles. Read get_users Liste les utilisateurs GLPI. Read kill_session Ferme proprement la session GLPI active. Read link_tickets Crée un lien entre deux tickets. Read list_followups Liste tous les suivis d'un ticket. Read list_itil_categories Liste toutes les catégories ITIL disponibles (Incident, Demande, Changement, Problème). Read list_kb_articles list_kb_articles Read list_kb_categories Liste toutes les categories de la base de connaissances. Read list_tasks Liste toutes les tâches d'un ticket. Read list_ticket_links Liste tous les liens d'un ticket avec d'autres tickets. Read list_tickets Liste les tickets avec pagination optionnelle. Read search_kb_articles search_kb_articles Read search_tickets Recherche avancée de tickets via l'API GLPI /search/Ticket. Read stats_by_category Retourne le nombre de tickets par catégorie ITIL. Read stats_by_priority Retourne le nombre de tickets ouverts par priorité. Read stats_by_status Retourne le nombre de tickets ouverts par statut. Read stats_overdue Retourne les tickets en retard (date d'échéance dépassée et non résolus). Read stats_resolution_time Retourne le délai moyen de résolution des tickets résolus ou clos.

Related servers

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

Questions about GLPI MCP

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

Yes. The GLPI MCP server exposes 2 destructive tools including delete_task, delete_ticket. 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 GLPI MCP? +

The GLPI MCP server has 15 write tools including add_followup, add_kb_article_visibility_group, add_kb_article_visibility_profile. 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 GLPI MCP.

How many tools does the GLPI MCP server expose? +

40 tools across 3 categories: Destructive, Read, Write. 23 are read-only. 17 can modify, create, or delete data.

How do I enforce a policy on GLPI MCP? +

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

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

Instant setup, no code required.

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.