List all LLM connections for the project.
AI agents call get_llm_connections 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 lists LLM connection information. It performs a query operation that returns data without modifying, deleting, or executing any actions. The 'get' prefix and 'list' verb confirm this is a read-only operation with minimal security risk unless connection details themselves are sensitive, which would be a data sensitivity concern rather than a functional risk category.
From the tool's definition Tool name contains 'get' and description states 'List all LLM connections', both indicating a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all LLM connections for the project. 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_llm_connections: 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_llm_connections 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_llm_connections 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_llm_connections. 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_llm_connections 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 →