Generates a call graph for a specific function.
AI agents call get_call_graph to retrieve information from Deobfuscate MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The get_call_graph tool performs static analysis to extract call relationship information from JavaScript code. It retrieves data about function dependencies and call flows without creating, modifying, deleting, or executing code. This is a classic Read operation: it queries the structure of existing code and returns analyzed data with no side effects.
From the tool's definition The tool 'generates a call graph for a specific function' - this is a read-only analysis operation that retrieves and displays function call relationships without modifying, executing, or deleting any code.
Documented attack patterns abuse exactly the kind of access get_call_graph gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Deobfuscate MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_call_graph:
{
"version": "1",
"default": "deny",
"tools": {
"get_call_graph": {}
}
}get_call_graph 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.
Generates a call graph for a specific function. It is categorised as a Read tool in the Deobfuscate MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Deobfuscate MCP Server MCP server in PolicyLayer and add a rule for get_call_graph: 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 Deobfuscate MCP Server. Nothing to install.
get_call_graph 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 get_call_graph 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 get_call_graph. 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.
get_call_graph is provided by the Deobfuscate MCP Server MCP server (madebytokens/deobfuscate-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Deobfuscate MCP Server, 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.
10 Deobfuscate MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.