Create or update an LLM connection (upsert by provider).
AI agents use upsert_llm_connection to create or update resources in Langfuse Mcp Python — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Langfuse Mcp Python environment.
This tool creates or updates (upserts) LLM connection configurations, which are data modifications. It does not delete data (thus not Destructive), does not move money (not Financial), does not execute arbitrary code (not Execute), and does not merely query (not Read).
From the tool's definition Tool name contains 'upsert' and description states 'Create or update an LLM connection', both indicating reversible data modification operations.
Attacks that exploit this kind of access
Create or update an LLM connection (upsert by provider). It is categorised as a Write tool in the Langfuse Mcp Python MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Langfuse Mcp Python MCP server in PolicyLayer and add a rule for upsert_llm_connection: 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.
upsert_llm_connection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the upsert_llm_connection 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 upsert_llm_connection. 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.
upsert_llm_connection 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 →