pcap_write

Write a compact classic PCAP file from deterministic packet byte records.

SERVERJshookmcp SOURCE@jshookmcp/jshook

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/io-github-vmoranv-jshookmcp/pcap-write.md

WHAT IT DOES

What pcap_write does on Jshookmcp

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

RISK

Why pcap_write is rated Medium

Creates or modifies PCAP file data reversibly; network packet captures could contain sensitive information but operation is not destructive.

From the tool's definition Write a compact classic PCAP file from deterministic packet byte records.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pcap_write safely

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

pcap_write Rate-limited

pcap_write 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": {
    "pcap_write": {
      "limits": [
        {
          "counter": "pcap_write_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 Jshookmcp, apply this rule, and every pcap_write call is checked against it from then on.

FAQ

Questions about pcap_write

What does the pcap_write tool do? +

Write a compact classic PCAP file from deterministic packet byte records. It is categorised as a Write tool in the Jshookmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pcap_write? +

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

What risk level is pcap_write? +

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

Can I rate-limit pcap_write? +

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

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

pcap_write is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools →

Across the catalogue

write_file on 0sec → The MCP Attack Database →

Guides

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