Create a library, trigger scan, or refresh metadata for an item
AI agents use manage_library 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.
The manage_library tool performs write operations: 'Create a library' directly creates new data structures, and 'refresh metadata' modifies existing data. These are reversible changes (metadata can be refreshed again, libraries can be removed), placing it in Write rather than Destructive.
From the tool's definition Tool description explicitly states 'Create a library, trigger scan, or refresh metadata for an item' — actions that modify or create data structures within the media server.
Documented attack patterns abuse exactly the kind of access manage_library 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 manage_library:
{
"version": "1",
"default": "deny",
"tools": {
"manage_library": {
"limits": [
{
"counter": "manage_library_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_library 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.
Create a library, trigger scan, or refresh metadata for an item. 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 manage_library: 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.
manage_library 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 manage_library 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 manage_library. 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.
manage_library 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.