AI agents call get_stack_trace to retrieve information from JVM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing stack trace information from a running JVM process. It does not execute arbitrary code, modify JVM state, delete data, or trigger financial transactions. It is a passive diagnostic query operation with no side effects, making it a Read category risk with low severity.
From the tool's definition Tool name 'get_stack_trace' and description 'Get thread stack trace information' indicate retrieval of diagnostic data with no modification or execution capabilities.
Documented attack patterns abuse exactly the kind of access get_stack_trace gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JVM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_stack_trace:
{
"version": "1",
"default": "deny",
"tools": {
"get_stack_trace": {}
}
}get_stack_trace 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.
Get thread stack trace information. It is categorised as a Read tool in the JVM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the JVM MCP Server MCP server in PolicyLayer and add a rule for get_stack_trace: 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 JVM MCP Server. Nothing to install.
get_stack_trace 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_stack_trace 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_stack_trace. 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_stack_trace is provided by the JVM MCP Server MCP server (xzq-xu/jvm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 JVM MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 JVM MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.