AI agents call lithtrix_blob_list 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 queries metadata about existing blobs without creating, modifying, deleting, or executing anything. It has no side effects and poses minimal risk even if misused by an AI agent, as it only returns informational metadata about stored objects. The GET method and list/metadata terminology confirm read-only semantics.
From the tool's definition Tool name includes 'list' and description states 'List blob metadata (GET /v1/blobs)' — a read-only retrieval operation using HTTP GET method with optional pagination parameters (page, per_page).
Attacks that exploit this kind of access
List blob metadata (GET /v1/blobs). Optional page and per_page. Requires LITHTRIX_API_KEY. 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_list: 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_list 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_list 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_list. 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_list 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 →