List all blob storage integrations (requires organization-scoped API key).
AI agents call get_blob_storage_integrations to retrieve information from Langfuse Mcp Python 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 blob storage integration metadata without creating, modifying, deleting, or executing anything. It is a straightforward read operation that returns information about existing integrations. The requirement for an organization-scoped API key indicates appropriate access control but does not change the operation's category.
From the tool's definition Tool name and description indicate it 'List[s] all blob storage integrations' with no modification or side effects mentioned. The verb 'List' is a classic Read operation.
Attacks that exploit this kind of access
List all blob storage integrations (requires organization-scoped API key). It is categorised as a Read tool in the Langfuse Mcp Python MCP Server, which means it retrieves data without modifying state.
Register the Langfuse Mcp Python MCP server in PolicyLayer and add a rule for get_blob_storage_integrations: 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 Langfuse Mcp Python. Nothing to install.
get_blob_storage_integrations 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 get_blob_storage_integrations 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 get_blob_storage_integrations. 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.
get_blob_storage_integrations is provided by the Langfuse Mcp Python MCP server (log-logn/langfuse-mcp-python). 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 →