run_get_ad_computers
A execute tool on the Pentester- MCP server.
This record as markdown: /tools/halilkirazkaya-pentester-mcp/run-get-ad-computers.md
What run_get_ad_computers does on Pentester-MCP
AI agents invoke run_get_ad_computers 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 run_get_ad_computers is rated High
The 'run_' prefix combined with the Pentester-MCP server context (which executes penetration testing tools) and the tool name referencing Active Directory enumeration indicates this executes a reconnaissance command. This is Execute rather than Read because it autonomously triggers external tooling with effects dependent on the target environment, not a simple query.
From the tool's definition Tool name 'run_get_ad_computers' contains 'run', and the server description explicitly states it 'enables AI assistants to autonomously execute over 200 open-source penetration testing tools' including 'reconnaissance'.
Attacks that exploit this kind of access
The rule that runs run_get_ad_computers safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pentester-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_get_ad_computers, this is the rule to start with:
run_get_ad_computers 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Pentester-MCP, apply this rule, and every run_get_ad_computers call is checked against it from then on.
Questions about run_get_ad_computers
run_get_ad_computers 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.
Register the Pentester MCP server in PolicyLayer and add a rule for run_get_ad_computers: 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.
run_get_ad_computers is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_get_ad_computers 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 run_get_ad_computers. 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.
run_get_ad_computers 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.
Across the catalogue