call_graph_analyze

Analyze runtime function call graph from in-page traces.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/call-graph-analyze.md

WHAT IT DOES

What call_graph_analyze does on Jshookmcp

AI agents call call_graph_analyze 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.

RISK

Why call_graph_analyze is rated Low

Tool retrieves and analyzes call graph data without modifying systems or executing arbitrary code.

From the tool's definition Analyze runtime function call graph from in-page traces.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs call_graph_analyze 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 call_graph_analyze, this is the rule to start with:

call_graph_analyze Allowed

call_graph_analyze is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "call_graph_analyze": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every call_graph_analyze call is checked against it from then on.

FAQ

Questions about call_graph_analyze

What does the call_graph_analyze tool do? +

Analyze runtime function call graph from in-page traces. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on call_graph_analyze? +

Register the Jshook MCP server in PolicyLayer and add a rule for call_graph_analyze: 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.

What risk level is call_graph_analyze? +

call_graph_analyze is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit call_graph_analyze? +

Yes. Add a rate_limit block to the call_graph_analyze 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.

How do I block call_graph_analyze completely? +

Set action: deny in the PolicyLayer policy for call_graph_analyze. 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.

What MCP server provides call_graph_analyze? +

call_graph_analyze 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.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →