AI agents invoke lithtrix_blob_parse to trigger actions in Lithtrix. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This is an Execute tool rather than Read because it performs a server-side operation (parsing via POST) that can trigger asynchronous jobs and external callbacks. While parsing itself is not inherently destructive, the ability to queue async work and invoke callbacks makes it an active operation beyond simple data retrieval.
From the tool's definition Tool performs POST request to extract/parse content from blobs with optional async execution via QStash and callback mechanisms.
Attacks that exploit this kind of access
POST /v1/blobs/{blob_id}/parse — extract text/tables; set async=true for QStash. Optional callback_url in JSON body. Requires LITHTRIX_API_KEY. It is categorised as a Execute tool in the Lithtrix MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Lithtrix MCP server in PolicyLayer and add a rule for lithtrix_blob_parse: 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_parse is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the lithtrix_blob_parse 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_parse. 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_parse 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 →