all_services_diagnostics · FlixBridge MCP: Risk & Policy

WHAT IT DOES

What all_services_diagnostics does on FlixBridge

AI agents invoke all_services_diagnostics to trigger actions in FlixBridge. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why all_services_diagnostics needs a policy

This tool does more than read data; it actively intervenes to fix stuck queue items across all connected media management services. The 'auto-fix' behavior constitutes an automated Execute action with potentially broad blast radius since it operates across all services simultaneously.

From the tool's definition 'Analyze and auto-fix stuck queue items across all services' — the 'auto-fix' action triggers external operations across multiple services

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

all_services_diagnostics Rate-limited

all_services_diagnostics stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "all_services_diagnostics": {
      "limits": [
        {
          "counter": "all_services_diagnostics_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about all_services_diagnostics

What does the all_services_diagnostics tool do? +

Analyze and auto-fix stuck queue items across all services. It is categorised as a Execute tool in the FlixBridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on all_services_diagnostics? +

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

What risk level is all_services_diagnostics? +

all_services_diagnostics is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit all_services_diagnostics? +

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

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

all_services_diagnostics is provided by the FlixBridge MCP server (thesammykins/flixbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.