multi_target_get_status

获取多目标协调系统状态

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

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/seac-25-kali-security-mcp/multi-target-get-status.md

WHAT IT DOES

What multi_target_get_status does on Kali Security MCP

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

RISK

Why multi_target_get_status is rated Low

This tool retrieves status information about a multi-target coordination system. It performs a read-only query operation typical of monitoring or diagnostic tools. While it operates within a penetration testing framework (Kali Security MCP), the specific function is passive information retrieval. No data is created, modified, deleted, or any external actions are triggered—only current state is queried.

From the tool's definition Tool name contains 'get_status' and description translates to 'Get multi-target coordination system status'. The 'get_' prefix and 'status' suffix indicate a retrieval operation with no state modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs multi_target_get_status 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 multi_target_get_status, this is the rule to start with:

multi_target_get_status Allowed

multi_target_get_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "multi_target_get_status": {}
  }
}

ALLOW ONLY 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 multi_target_get_status call is checked against it from then on.

FAQ

Questions about multi_target_get_status

What does the multi_target_get_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 multi_target_get_status? +

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

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

Can I rate-limit multi_target_get_status? +

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

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

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

KEEP EXPLORING

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

This server

All 194 Kali Security tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →