delete_mcp_json

Delete an MCP JSON configuration by its ID. This action is irreversible. Use cases: - Remove obsolete configurations - Clean up test data - Remove incorrectly created configurations

Server Langfuse Observability langfuse-observability-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_mcp_json does on Langfuse Observability

AI agents call delete_mcp_json 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 delete_mcp_json needs a policy

This tool permanently removes configuration data with no undo capability. While the blast radius depends on what configurations exist and their criticality to system operations, the irreversible nature and potential to corrupt observability/system setup justifies 'high' severity.

From the tool's definition Tool description explicitly states 'Delete an MCP JSON configuration by its ID. This action is irreversible.' The irreversibility qualifier and the word 'Delete' unambiguously indicate data destruction without recovery option.

Questions about delete_mcp_json

What does the delete_mcp_json tool do? +

Delete an MCP JSON configuration by its ID. This action is irreversible. Use cases: - Remove obsolete configurations - Clean up test data - Remove incorrectly created configurations. 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 delete_mcp_json? +

Register the Langfuse Observability MCP server in PolicyLayer and add a rule for delete_mcp_json: 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 delete_mcp_json? +

delete_mcp_json 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 delete_mcp_json? +

Yes. Add a rate_limit block to the delete_mcp_json 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 delete_mcp_json completely? +

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

delete_mcp_json 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.