merge_tickets · GLPI MCP: Risk & Policy

WHAT IT DOES

What merge_tickets does on GLPI MCP

AI agents use merge_tickets to create or update resources in GLPI MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GLPI MCP environment.

WHY IT NEEDS A POLICY

Why merge_tickets needs a policy

An AI agent can call merge_tickets faster than any human can review — one bad instruction and it creates or modifies resources in GLPI MCP by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

merge_tickets Rate-limited

merge_tickets stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "merge_tickets": {
      "limits": [
        {
          "counter": "merge_tickets_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GLPI MCP, so you can run agents against it safely.

FAQ

Questions about merge_tickets

What does the merge_tickets tool do? +

merge_tickets. It is categorised as a Write tool in the GLPI MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on merge_tickets? +

Register the GLPI MCP server in PolicyLayer and add a rule for merge_tickets: 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 GLPI MCP. Nothing to install.

What risk level is merge_tickets? +

merge_tickets is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit merge_tickets? +

Yes. Add a rate_limit block to the merge_tickets 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 merge_tickets completely? +

Set action: deny in the PolicyLayer policy for merge_tickets. 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 merge_tickets? +

merge_tickets is provided by the GLPI MCP server (svtica/glpi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.