Parses a .jfr file and returns a structured summary: top methods by CPU samples, GC statistics, thread allocation stats, and anomaly hints (e.g. high GC count). Use for a quick high-level overview of the recording before diving into specific profiles.
Accepts file system path (filepath)
Part of the Javaperf MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke parse_jfr_summary to trigger processes or run actions in Javaperf. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
parse_jfr_summary can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
parse_jfr_summary:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Javaperf policy for all 15 tools.
Agents calling execute-class tools like parse_jfr_summary have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
parse_jfr_summary is one of the high-risk operations in Javaperf. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Parses a .jfr file and returns a structured summary: top methods by CPU samples, GC statistics, thread allocation stats, and anomaly hints (e.g. high GC count). Use for a quick high-level overview of the recording before diving into specific profiles.. It is categorised as a Execute tool in the Javaperf MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for parse_jfr_summary. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Javaperf MCP server.
parse_jfr_summary is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the parse_jfr_summary rule in your Intercept 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 Intercept policy for parse_jfr_summary. 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.
parse_jfr_summary is provided by the Javaperf MCP server (javaperf). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept