Attach to an existing process by PID using GDB/MI. Args: pid: Target process ID to attach to. Returns: (result, context) where result is the MI attach result and context is a list of quick context snapshots (e.g., backtrace/heap) captured immediately after attach.
AI agents invoke attach to trigger actions in Pwno. 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.
This tool attaches a debugger (GDB) to a live process by PID, which is an active external operation that can inspect, pause, or manipulate the target process. This goes beyond reading — attaching with GDB gives full control over the process (memory reads/writes, breakpoints, execution control).
From the tool's definition Attach to an existing process by PID using GDB/MI
Documented attack patterns abuse exactly the kind of access attach gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pwno, and nothing reaches the server without passing your rules. This is the rule we recommend for attach:
{
"version": "1",
"default": "deny",
"tools": {
"attach": {
"limits": [
{
"counter": "attach_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}attach 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.
Attach to an existing process by PID using GDB/MI. Args: pid: Target process ID to attach to. Returns: (result, context) where result is the MI attach result and context is a list of quick context snapshots (e.g., backtrace/heap) captured immediately after attach. It is categorised as a Execute tool in the Pwno MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pwno MCP server in PolicyLayer and add a rule for attach: 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 Pwno. Nothing to install.
attach 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 attach 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 attach. 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.
attach is provided by the Pwno MCP server (pwno-io/pwno-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 Pwno tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 Pwno tools catalogued and risk-classified — across an index of 42,500+ MCP servers.