dart_list_functions
List all Dart Code objects (compiled functions) from a loaded snapshot, with entry point address, size, and name (if available). Pass a sessionId to reuse a cached snapshot.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/dart-list-functions.md
What dart_list_functions does on Jshookmcp
AI agents call dart_list_functions to retrieve information from Jshookmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why dart_list_functions is rated Low
Queries and retrieves metadata from a loaded snapshot without modifying or executing code.
From the tool's definition List all Dart Code objects, entry point address, size, name
Attacks that exploit this kind of access
The rule that runs dart_list_functions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dart_list_functions, this is the rule to start with:
dart_list_functions 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 Jshookmcp, apply this rule, and every dart_list_functions call is checked against it from then on.
Questions about dart_list_functions
List all Dart Code objects (compiled functions) from a loaded snapshot, with entry point address, size, and name (if available). Pass a sessionId to reuse a cached snapshot. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.
Register the Jshook MCP server in PolicyLayer and add a rule for dart_list_functions: 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 Jshookmcp. Nothing to install.
dart_list_functions 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 dart_list_functions 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 dart_list_functions. 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.
dart_list_functions is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Jshook, and thousands of servers like it.
This server
Across the catalogue