Verify tshark/capinfos installation and configuration.
AI agents call pm_check_install to retrieve information from PacketMaster without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool verifies the presence and configuration of installed utilities (tshark/capinfos) by querying system state. This is a read-only diagnostic operation with no side effects, no code execution capability, and no data modification. The blast radius if misused is minimal—it can only retrieve installation status information.
From the tool's definition Tool name 'pm_check_install' and description 'Verify tshark/capinfos installation and configuration' indicate a diagnostic/inspection operation that checks system state without modifying or executing arbitrary code.
Attacks that exploit this kind of access
Verify tshark/capinfos installation and configuration. It is categorised as a Read tool in the PacketMaster MCP Server, which means it retrieves data without modifying state.
Register the PacketMaster MCP server in PolicyLayer and add a rule for pm_check_install: 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 PacketMaster. Nothing to install.
pm_check_install is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pm_check_install 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.
Set action: deny in the PolicyLayer policy for pm_check_install. 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.
pm_check_install is provided by the PacketMaster MCP server (jctechbr/packetmaster). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →