remove_servers_from_tenant · Langfuse Observability MCP

WHAT IT DOES

What remove_servers_from_tenant does on Langfuse Observability

AI agents call remove_servers_from_tenant to permanently remove resources in Langfuse Observability — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

WHY IT NEEDS A POLICY

Why remove_servers_from_tenant needs a policy

Removing servers from a tenant is a destructive operation that disassociates or deletes server configurations from a tenant, which is not easily reversible and could disrupt services or lose configuration data. This warrants a high severity rating due to the blast radius of potentially breaking tenant functionality.

From the tool's definition 'Remove MCP servers from a tenant' — the word 'remove' indicates an irreversible deletion of server associations from a tenant

Attacks that exploit this kind of access

Questions about remove_servers_from_tenant

What does the remove_servers_from_tenant tool do? +

Remove MCP servers from a tenant. It is categorised as a Destructive tool in the Langfuse Observability MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_servers_from_tenant? +

Register the Langfuse Observability MCP server in PolicyLayer and add a rule for remove_servers_from_tenant: 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 Observability. Nothing to install.

What risk level is remove_servers_from_tenant? +

remove_servers_from_tenant is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_servers_from_tenant? +

Yes. Add a rate_limit block to the remove_servers_from_tenant 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.

How do I block remove_servers_from_tenant completely? +

Set action: deny in the PolicyLayer policy for remove_servers_from_tenant. 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.

What MCP server provides remove_servers_from_tenant? +

remove_servers_from_tenant is provided by the Langfuse Observability MCP server (langfuse-observability-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.