Show the kernel base address.
AI agents call pwndbg_kbase to retrieve information from Pwndbg Lldb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and displays the kernel base address from the debugger state. It performs a straightforward information retrieval operation with no capability to modify, execute code, or cause destructive changes. The blast radius is minimal—an AI agent misusing this tool can only read debug metadata that would typically be available to someone with debugger access already granted.
From the tool's definition Tool name 'pwndbg_kbase' and description 'Show the kernel base address' indicate a query operation that retrieves debugging information. No side effects, modifications, or code execution implied.
Attacks that exploit this kind of access
Show the kernel base address. It is categorised as a Read tool in the Pwndbg Lldb MCP Server, which means it retrieves data without modifying state.
Register the Pwndbg Lldb MCP server in PolicyLayer and add a rule for pwndbg_kbase: 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 Pwndbg Lldb. Nothing to install.
pwndbg_kbase is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pwndbg_kbase 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 pwndbg_kbase. 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.
pwndbg_kbase is provided by the Pwndbg Lldb MCP server (micro-evaluation-group/pwndbg-lldb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →