list_hooks
List all active hooks.
This record as markdown: /tools/0xhackerfren-frida-game-hacking-mcp/list-hooks.md
What list_hooks does on Frida Game Hacking MCP
AI agents call list_hooks to retrieve information from Frida Game Hacking MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_hooks is rated Low
This tool performs a read-only operation—it queries and returns information about active hooks without creating, modifying, deleting, or executing anything. While it operates in a sensitive security context (Frida game hacking), the tool itself is observational and has no side effects.
From the tool's definition The tool name 'list_hooks' and description 'List all active hooks' indicate a query/enumeration operation that retrieves information about existing hooks without modifying state.
Attacks that exploit this kind of access
The rule that runs list_hooks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frida Game Hacking MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_hooks, this is the rule to start with:
list_hooks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Frida Game Hacking MCP, apply this rule, and every list_hooks call is checked against it from then on.
Questions about list_hooks
List all active hooks. It is categorised as a Read tool in the Frida Game Hacking MCP MCP Server, which means it retrieves data without modifying state.
Register the Frida Game Hacking MCP server in PolicyLayer and add a rule for list_hooks: 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 Frida Game Hacking MCP. Nothing to install.
list_hooks 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_hooks 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_hooks. 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_hooks is provided by the Frida Game Hacking MCP server (0xhackerfren/frida-game-hacking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Frida Game Hacking, and thousands of servers like it.
This server
Across the catalogue