stats_by_assignee · GLPI MCP: Risk & Policy

WHAT IT DOES

What stats_by_assignee does on GLPI MCP

AI agents use stats_by_assignee 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 stats_by_assignee needs a policy

An AI agent can call stats_by_assignee 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

stats_by_assignee Rate-limited

stats_by_assignee 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": {
    "stats_by_assignee": {
      "limits": [
        {
          "counter": "stats_by_assignee_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 stats_by_assignee

What does the stats_by_assignee tool do? +

Retourne le nombre de tickets par technicien assigné. 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 stats_by_assignee? +

Register the GLPI MCP server in PolicyLayer and add a rule for stats_by_assignee: 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 stats_by_assignee? +

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

Can I rate-limit stats_by_assignee? +

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

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

stats_by_assignee 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.