manual_import · FlixBridge MCP: Risk & Policy

WHAT IT DOES

What manual_import does on FlixBridge

AI agents use manual_import to create or update resources in FlixBridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FlixBridge environment.

WHY IT NEEDS A POLICY

Why manual_import needs a policy

This tool creates or modifies data (imports media into libraries) which is reversible through deletion or re-organization, placing it in Write rather than Execute or Destructive. The 'preview' capability suggests intentional data changes.

From the tool's definition Tool description states 'execute high-confidence ARR manual imports for queue items'. The term 'execute' combined with 'import' indicates the tool modifies library state by adding/organizing media content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manual_import Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "manual_import": {
      "limits": [
        {
          "counter": "manual_import_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 manual_import

What does the manual_import tool do? +

Preview and execute high-confidence ARR manual imports for queue items. It is categorised as a Write tool in the FlixBridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on manual_import? +

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

manual_import is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit manual_import? +

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

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

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