Low Risk

parse_tool_output

Parse common pentest tool outputs (nmap XML, JSON, etc.)

How to control parse_tool_output ↓

What parse_tool_output does on Pentest MCP Server

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

Low Risk

Why parse_tool_output needs a policy

This tool parses and interprets existing tool output files (XML, JSON formats). It reads and processes data without executing commands, modifying systems, or causing side effects. The action is purely analytical/interpretive on already-collected data. Severity is low as misuse only reveals information already captured in output files.

From the tool's definition Parse common pentest tool outputs (nmap XML, JSON, etc.)

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

How to control parse_tool_output

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

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

parse_tool_output 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 Pentest MCP Server — 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.

Related tools and policies

Go deeper

Questions about parse_tool_output

What does the parse_tool_output tool do? +

Parse common pentest tool outputs (nmap XML, JSON, etc.). It is categorised as a Read tool in the Pentest MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on parse_tool_output? +

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

What risk level is parse_tool_output? +

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

Can I rate-limit parse_tool_output? +

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

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

parse_tool_output is provided by the Pentest MCP Server MCP server (layesec006/pentest-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pentest MCP Server tool call.

Start from Pentest MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

12 Pentest MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.