log_attack_step

A write tool on the Kali Security MCP server.

SERVERKali Security MCP SOURCEseac-25/kali-security-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/seac-25-kali-security-mcp/log-attack-step.md

WHAT IT DOES

What log_attack_step does on Kali Security MCP

AI agents use log_attack_step to create or update resources in Kali Security MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kali Security MCP environment.

RISK

Why log_attack_step is rated Medium

The name suggests logging/recording an attack step, which is a write operation (creating or updating log/audit data). The empty description lowers confidence significantly. Given the server context (penetration testing, 193 Kali tools, attack workflows), even a logging tool could record sensitive offensive security data.

From the tool's definition Tool name 'log_attack_step' on a penetration testing server; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs log_attack_step safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Kali Security MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For log_attack_step, this is the rule to start with:

log_attack_step Rate-limited

log_attack_step stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "log_attack_step": {
      "limits": [
        {
          "counter": "log_attack_step_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Kali Security MCP, apply this rule, and every log_attack_step call is checked against it from then on.

FAQ

Questions about log_attack_step

What does the log_attack_step tool do? +

log_attack_step is a write tool on the Kali Security MCP server. It is categorised as a Write tool in the Kali Security MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on log_attack_step? +

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

What risk level is log_attack_step? +

log_attack_step is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit log_attack_step? +

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

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

log_attack_step is provided by the Kali Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Kali Security, and thousands of servers like it.

This server

All 194 Kali Security tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →