AI agents call lithtrix_blob_meta 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 performs a straightforward metadata retrieval operation. It queries an existing blob's metadata without modifying, deleting, or executing any operations. The GET HTTP method and description confirm it is purely informational. The requirement for LITHTRIX_API_KEY provides access control but does not change the read-only nature.
From the tool's definition Tool retrieves JSON metadata for a blob via GET request to /v1/blobs/{blob_id}/meta. GET operations are read-only with no side effects.
Attacks that exploit this kind of access
Get JSON metadata for one blob (GET /v1/blobs/{blob_id}/meta). 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_meta: 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_meta 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_meta 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_meta. 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_meta 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 →