List segments/sections. Returns fields: name, vaddr, paddr, size, perm.
AI agents call list_segments to retrieve information from CutterMCP-plus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves structural information about a binary's memory layout and section metadata. It performs no modifications, executions, deletions, or financial operations. The blast radius of misuse is minimal—an agent could map binary structure for analysis, but cannot execute code, alter data, or cause irreversible harm through listing alone. This is a straightforward Read operation.
From the tool's definition Tool description states "List segments/sections. Returns fields: name, vaddr, paddr, size, perm." The verb "List" and the read-only return of binary metadata (virtual address, physical address, size, permissions) indicate retrieval without modification or…
Documented attack patterns abuse exactly the kind of access list_segments gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CutterMCP-plus, and nothing reaches the server without passing your rules. This is the rule we recommend for list_segments:
{
"version": "1",
"default": "deny",
"tools": {
"list_segments": {}
}
}list_segments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List segments/sections. Returns fields: name, vaddr, paddr, size, perm. It is categorised as a Read tool in the CutterMCP-plus MCP Server, which means it retrieves data without modifying state.
Register the CutterMCP-plus MCP server in PolicyLayer and add a rule for list_segments: 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 CutterMCP-plus. Nothing to install.
list_segments 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 list_segments 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 list_segments. 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.
list_segments is provided by the CutterMCP-plus MCP server (restkhz/cuttermcp-plus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 20 CutterMCP-plus tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
20 CutterMCP-plus tools catalogued and risk-classified — across an index of 42,500+ MCP servers.