plan_tools

A execute tool on the Pentest Ai MCP server.

SERVERPentest Ai SOURCE0xsteph/pentest-ai

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xsteph-pentest-ai/plan-tools.md

WHAT IT DOES

What plan_tools does on Pentest Ai

AI agents invoke plan_tools to trigger actions in Pentest Ai. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why plan_tools is rated High

The server context is explicitly a pentesting automation platform that executes real security tools and exploits. A tool named 'plan_tools' on such a server most likely plans or selects which security tools to run against a target, which falls under Execute. However, the empty description significantly lowers confidence — it could also be a Read/planning step.

From the tool's definition Tool name 'plan_tools' on a pentesting server (pentest-ai) described as running 'real security tools' and 'working PoCs'. No description provided.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs plan_tools safely

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

plan_tools Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pentest Ai, apply this rule, and every plan_tools call is checked against it from then on.

FAQ

Questions about plan_tools

What does the plan_tools tool do? +

plan_tools is a execute tool on the Pentest Ai MCP server. It is categorised as a Execute tool in the Pentest Ai MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on plan_tools? +

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

What risk level is plan_tools? +

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

Can I rate-limit plan_tools? +

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

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

plan_tools is provided by the Pentest Ai MCP server (0xsteph/pentest-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pentest Ai, and thousands of servers like it.

This server

All 51 Pentest Ai tools → High-risk tools on this server →

Across the catalogue

team_manager_approve_plan on Team Manager MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →