activity_log

THE RISK

Low Risk

Why activity_log needs a policy

This tool is a read-only operation that queries and displays historical activity logs. It returns data about past events (viewing history, authentication events, library modifications) without creating, modifying, deleting, or executing anything. The activity log itself is not altered by reading it.

From the tool's definition Tool retrieves 'recent server activity: who watched what, logins, library changes' - purely informational queries with no modification or side effects.

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

POLICY

How to control activity_log

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 activity_log:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "activity_log": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Mediabox MCP tools

Destructive cancel_downloads Manage Sonarr/Radarr/qBittorrent download queues. NOT for PyLoad — use download_status act Destructive cleanup_server Clean up the server: remove Jellyfin cache, temp files, orphan downloads, ghost entries in Destructive movie_remove Remove a movie from Radarr Destructive series_remove Remove a series from Sonarr Destructive manage_files List, move, or delete files and folders. Paths starting with Execute download_direct Download a file from a direct URL (or YouTube/video site via yt-dlp) and optionally organi Execute download_status PyLoad download manager. Three actions: - status: shows PyLoad queue AND lists folders in Execute fix_subtitles Convert ASS/SSA subtitles to SRT in MKV files to prevent transcoding. Works on single file

All 30 Mediabox MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about activity_log

What does the activity_log tool do? +

Recent server activity: who watched what, logins, library changes. 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 activity_log? +

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

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

Can I rate-limit activity_log? +

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

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

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

CHECK YOUR STACK →