AI agents call imhex_list_files to retrieve information from ImHex MCP Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple enumeration/listing of files already open in the ImHex application. It has no side effects, does not execute code, does not modify data, and does not delete anything.
From the tool's definition Tool name 'imhex_list_files' combined with description 'List all currently open files in ImHex' indicates a query operation that retrieves information about open files without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access imhex_list_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ImHex MCP Integration, and nothing reaches the server without passing your rules. This is the rule we recommend for imhex_list_files:
{
"version": "1",
"default": "deny",
"tools": {
"imhex_list_files": {}
}
} imhex_list_files 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 all currently open files in ImHex. It is categorised as a Read tool in the ImHex MCP Integration MCP Server, which means it retrieves data without modifying state.
Register the ImHex MCP Integration MCP server in PolicyLayer and add a rule for imhex_list_files: 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 ImHex MCP Integration. Nothing to install.
imhex_list_files 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 imhex_list_files 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 imhex_list_files. 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.
imhex_list_files is provided by the ImHex MCP Integration MCP server (jmpnop/imhexmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ImHex MCP Integration, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
27 ImHex MCP Integration tools catalogued and risk-classified — across an index of 43,000+ MCP servers.