one_gadget_search
A execute tool on the Pengstrike MCP server.
This record as markdown: /tools/pengstrike-mcp/one-gadget-search.md
What one_gadget_search does on Pengstrike
AI agents invoke one_gadget_search to trigger actions in Pengstrike. 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 one_gadget_search is rated High
The tool name strongly suggests it searches for 'one gadgets' (also called magic gadgets), which are offsets in libc that allow an attacker to spawn a shell with a single pointer overwrite.
From the tool's definition Tool name 'one_gadget_search' — 'one_gadget' is a well-known exploit technique for finding ROP gadgets in libc to achieve arbitrary code execution; description is empty/uninformative.
Attacks that exploit this kind of access
The rule that runs one_gadget_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pengstrike, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For one_gadget_search, this is the rule to start with:
one_gadget_search 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 Pengstrike, apply this rule, and every one_gadget_search call is checked against it from then on.
Questions about one_gadget_search
one_gadget_search is a execute tool on the Pengstrike MCP server. It is categorised as a Execute tool in the Pengstrike MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pengstrike MCP server in PolicyLayer and add a rule for one_gadget_search: 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 Pengstrike. Nothing to install.
one_gadget_search 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 one_gadget_search 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 one_gadget_search. 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.
one_gadget_search is provided by the Pengstrike MCP server (wangqiongpeng/pengstrike-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pengstrike, and thousands of servers like it.
Across the catalogue