AI agents invoke run_sherlock 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.
Sherlock is a widely-used open-source OSINT tool that performs username enumeration across hundreds of social media platforms. Given the server context (pentesting, reconnaissance, exploitation), this tool likely executes the Sherlock binary to perform active reconnaissance against external targets.
From the tool's definition Tool name 'run_sherlock' on a penetration testing server that 'autonomously execute[s] over 200 open-source penetration testing tools'; Sherlock is a well-known OSINT reconnaissance tool used to hunt usernames across social networks.
Documented attack patterns abuse exactly the kind of access run_sherlock gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pentester-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for run_sherlock:
{
"version": "1",
"default": "deny",
"tools": {
"run_sherlock": {
"limits": [
{
"counter": "run_sherlock_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_sherlock 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.
Free to start. No card required.
run_sherlock. 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_sherlock: 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_sherlock 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_sherlock 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_sherlock. 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_sherlock 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.
Start from Pentester-MCP, 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.
337 Pentester-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.