Low Risk

adaptive_get_execution_status

获取执行上下文状态

How to control adaptive_get_execution_status ↓

AI agents call adaptive_get_execution_status to retrieve information from Kali Security MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves or queries the status of an execution context. It has no side effects—it does not create, modify, delete, or execute anything. It falls clearly into the Read category as a status-checking operation. In the context of a penetration testing framework, status queries are foundational but low-risk when isolated.

From the tool's definition Tool name 'adaptive_get_execution_status' and description 'get execution context status' indicate a query/retrieval operation that checks the state of an execution context without modifying it.

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "adaptive_get_execution_status": {}
  }
}

adaptive_get_execution_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Kali Security MCP — 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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the adaptive_get_execution_status tool do? +

获取执行上下文状态. It is categorised as a Read tool in the Kali Security MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on adaptive_get_execution_status? +

Register the Kali Security MCP server in PolicyLayer and add a rule for adaptive_get_execution_status: 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 adaptive_get_execution_status? +

adaptive_get_execution_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit adaptive_get_execution_status? +

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

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

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

Enforce policy on every Kali Security MCP tool call.

Deterministic rules across all 249 Kali Security MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

249 Kali Security MCP tools catalogued and risk-classified — across an index of 42,500+ 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.