Check for import issues and stuck downloads
AI agents call import_issues to retrieve information from FlixBridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool checks and reports on import issues and stuck downloads. This is a read/diagnostic operation that retrieves status information without modifying, executing, or deleting anything.
From the tool's definition 'Check for import issues and stuck downloads' — purely diagnostic/monitoring, no modification implied
Attacks that exploit this kind of access
Check for import issues and stuck downloads. It is categorised as a Read tool in the FlixBridge MCP Server, which means it retrieves data without modifying state.
Register the FlixBridge MCP server in PolicyLayer and add a rule for import_issues: 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.
import_issues is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the import_issues 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 import_issues. 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.
import_issues 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →