Read raw bytes at the given address. Default size is 64.
AI agents call read_bytes 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 retrieves binary data from a target program's memory or binary file at a specified address, similar to a disassembler's read operation. It has no side effects, does not modify state, and performs no external operations. It is purely informational/analytical in nature, consistent with the reverse engineering analysis purpose of the CutterMCP-plus server.
From the tool's definition Tool name 'read_bytes' and description 'Read raw bytes at the given address' explicitly indicate data retrieval without modification. The default size parameter (64 bytes) further confirms a bounded query operation.
Documented attack patterns abuse exactly the kind of access read_bytes 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 read_bytes:
{
"version": "1",
"default": "deny",
"tools": {
"read_bytes": {}
}
}read_bytes 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.
Read raw bytes at the given address. Default size is 64. 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 read_bytes: 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.
read_bytes 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 read_bytes 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 read_bytes. 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.
read_bytes 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.