restart_kafka_connector_task

THE RISK

High Risk

Why restart_kafka_connector_task needs a policy

Restarting a Kafka connector task is an Execute-category action because it triggers an external operation whose effects depend on the connector configuration and state. While the description is empty (lowering confidence slightly), the tool name and server context (Kafka cluster management) clearly indicate this performs an operational trigger rather than a simple read or reversible write.

From the tool's definition Tool name 'restart_kafka_connector_task' indicates triggering/restarting an external operation (Kafka connector task).

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

POLICY

How to control restart_kafka_connector_task

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 restart_kafka_connector_task:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "restart_kafka_connector_task": {
      "limits": [
        {
          "counter": "restart_kafka_connector_task_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

restart_kafka_connector_task stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

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

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Lenses MCP Server tools

Destructive delete_consumer_group Delete a consumer group. Destructive delete_consumer_group_offsets delete_consumer_group_offsets Destructive delete_consumer_partition_offset delete_consumer_partition_offset Destructive delete_kafka_connector Deletes a Kafka connector. Destructive delete_sql_processor Removes an existing SQL processor. Execute execute_sql Executes SQL statements/queries using Lenses WebSocket API. Execute resend_message resend_message Execute create_sql_processor create_sql_processor

All 42 Lenses MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Lenses MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about restart_kafka_connector_task

What does the restart_kafka_connector_task tool do? +

restart_kafka_connector_task. It is categorised as a Execute tool in the Lenses MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on restart_kafka_connector_task? +

Register the Lenses MCP Server MCP server in PolicyLayer and add a rule for restart_kafka_connector_task: 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 restart_kafka_connector_task? +

restart_kafka_connector_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit restart_kafka_connector_task? +

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

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

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

CHECK YOUR STACK →