AI agents call lithtrix_blob_download to retrieve information from Lithtrix without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns blob content without side effects. It performs a read-only operation that queries and fetches data from a persistent storage system. The GET method semantics and return of existing content (content_base64, content_type) confirm this is a pure read operation with no destructive, write, or execute capabilities.
From the tool's definition Tool name 'lithtrix_blob_download' and description 'Download blob bytes (GET /v1/blobs/{blob_id}). Returns JSON with content_base64 and content_type.' indicate a retrieval operation using GET HTTP method with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
Download blob bytes (GET /v1/blobs/{blob_id}). Returns JSON with content_base64 and content_type. It is categorised as a Read tool in the Lithtrix MCP Server, which means it retrieves data without modifying state.
Register the Lithtrix MCP server in PolicyLayer and add a rule for lithtrix_blob_download: 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 Lithtrix. Nothing to install.
lithtrix_blob_download 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 lithtrix_blob_download 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 lithtrix_blob_download. 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.
lithtrix_blob_download is provided by the Lithtrix MCP server (lithtrix/lithtrix-mcp). 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 →