Get download/import history details
AI agents call history_detail 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.
This tool retrieves and queries download/import history information. It performs a read-only operation with no side effects, no data modification, and no irreversible actions. The verb 'Get' and focus on retrieving 'details' confirms it is a retrieval operation. Severity is low as misuse would only expose historical information without enabling destructive or financial actions.
From the tool's definition Tool name 'history_detail' and description 'Get download/import history details' indicate retrieval of existing historical data with no modification, creation, or deletion of records.
Attacks that exploit this kind of access
Get download/import history details. 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 history_detail: 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.
history_detail 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 history_detail 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 history_detail. 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.
history_detail 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 →