Rename episode files to Jellyfin standard format. Searches recursively. You can pass jellyfinItemId instead of showPath — the tool resolves the path from Jellyfin automatically. Use search_media first to find the item ID if needed.
AI agents use rename_episodes to create or update resources in Mediabox MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mediabox MCP environment.
File renaming is a Write operation—it creates a modified state of the filesystem (new filenames) reversibly. While recursive directory traversal increases the scope, the operation itself is not Destructive (files are not deleted, only renamed) and not Destructive if errors occur (the original naming can typically be recovered or re-run).
From the tool's definition rename_episodes performs file renaming operations ("Rename episode files"), which modifies existing files by changing their names. This is a write operation that reversibly alters metadata/names without deleting data.
Documented attack patterns abuse exactly the kind of access rename_episodes gives an agent:
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 rename_episodes:
{
"version": "1",
"default": "deny",
"tools": {
"rename_episodes": {
"limits": [
{
"counter": "rename_episodes_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}rename_episodes 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.
Free to start. No card required.
Rename episode files to Jellyfin standard format. Searches recursively. You can pass jellyfinItemId instead of showPath — the tool resolves the path from Jellyfin automatically. Use search_media first to find the item ID if needed. It is categorised as a Write tool in the Mediabox MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mediabox MCP server in PolicyLayer and add a rule for rename_episodes: 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.
rename_episodes is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the rename_episodes 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.
Set action: deny in the PolicyLayer policy for rename_episodes. 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.
rename_episodes 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.
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.