Low Risk

server_status

Complete server overview: Jellyfin info, disk usage, per-library stats, active sessions, and users

How to control server_status ↓

What server_status does on Mediabox MCP

AI agents call server_status to retrieve information from Mediabox MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why server_status needs a policy

This tool only reads and aggregates existing server state and statistics. It performs no create, modify, delete, execute, or financial operations. The information retrieved could theoretically inform decisions about the system, but the tool itself is purely observational with minimal blast radius if misused by an agent.

From the tool's definition Tool provides 'Complete server overview' including 'Jellyfin info, disk usage, per-library stats, active sessions, and users' — all retrieval/query operations with no modification or side effects.

Documented attack patterns abuse exactly the kind of access server_status gives an agent:

How to control server_status

PolicyLayer is an MCP gateway — it sits between your AI agents and Mediabox MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for server_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "server_status": {}
  }
}

server_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mediabox MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about server_status

What does the server_status tool do? +

Complete server overview: Jellyfin info, disk usage, per-library stats, active sessions, and users. It is categorised as a Read tool in the Mediabox MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on server_status? +

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

What risk level is server_status? +

server_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit server_status? +

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

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

server_status is provided by the Mediabox MCP server (juancmpdev/mediabox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mediabox MCP tool call.

Start from Mediabox MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

30 Mediabox 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.