Critical Risk →

delete_sql_processor

Removes an existing SQL processor.

How to control delete_sql_processor ↓

What delete_sql_processor does on Lenses MCP Server

AI agents call delete_sql_processor to permanently remove resources in Lenses MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_sql_processor needs a policy

The tool permanently deletes a SQL processor, which cannot be undone. This is an irreversible operation that destroys configuration and potentially associated processing logic. While it does not affect data directly in Kafka topics (unlike delete_consumer_group or similar data-deletion tools), it permanently removes infrastructure/application state.

From the tool's definition Tool name 'delete_sql_processor' and description 'Removes an existing SQL processor' directly indicate irreversible deletion of a resource.

Documented attack patterns abuse exactly the kind of access delete_sql_processor gives an agent:

How to control delete_sql_processor

PolicyLayer is an MCP gateway — it sits between your AI agents and Lenses MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_sql_processor:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_sql_processor"
  ]
}

delete_sql_processor disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Lenses MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_sql_processor

What does the delete_sql_processor tool do? +

Removes an existing SQL processor. It is categorised as a Destructive tool in the Lenses MCP Server 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_sql_processor? +

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

What risk level is delete_sql_processor? +

delete_sql_processor 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_sql_processor? +

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

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

delete_sql_processor is provided by the Lenses MCP Server MCP server (lensesio/lenses-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Lenses MCP Server tool call.

Start from Lenses MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

42 Lenses MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.