New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

start_bruteshark_live

A execute tool on the Pentester- MCP server.

SERVERPentester-MCP SOURCEhalilkirazkaya/pentester-mcp
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/halilkirazkaya-pentester-mcp/start-bruteshark-live.md

What start_bruteshark_live does on Pentester-MCP

AI agents invoke start_bruteshark_live to trigger actions in Pentester-MCP. 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.

Why start_bruteshark_live is rated High

Bruteshark is used for credential extraction and brute-force attacks against captured network traffic or live streams. Starting it 'live' means initiating active brute-forcing operations whose effects depend on network conditions and target systems. This is Execute-category because it triggers external security testing operations with unpredictable outcomes.

From the tool's definition Tool name 'start_bruteshark_live' indicates launching Bruteshark (a network traffic analysis and brute-force tool).

Questions about start_bruteshark_live

What does the start_bruteshark_live tool do? +

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

How do I enforce a policy on start_bruteshark_live? +

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

What risk level is start_bruteshark_live? +

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

Can I rate-limit start_bruteshark_live? +

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

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

start_bruteshark_live is provided by the Pentester MCP server (halilkirazkaya/pentester-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Pentester, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Pentester's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.