java_async_alloc_profile · Heap Seance MCP: Risk & Policy

WHAT IT DOES

What java_async_alloc_profile does on Heap Seance

AI agents invoke java_async_alloc_profile to trigger actions in Heap Seance. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why java_async_alloc_profile needs a policy

Based on the server description, this tool runs async-profiler to capture allocation profiles on a live Java process. This constitutes executing an external profiling operation against a running JVM. The description is empty, lowering confidence, but the sibling tools (jfr_start, heap_dump) and server context strongly suggest this triggers an active profiling session.

From the tool's definition Tool name 'java_async_alloc_profile' combined with server context describing 'async-profiler allocation profiles' — implies triggering an async-profiler agent against a live JVM process.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

java_async_alloc_profile Rate-limited

java_async_alloc_profile stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "java_async_alloc_profile": {
      "limits": [
        {
          "counter": "java_async_alloc_profile_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Heap Seance, so you can run agents against it safely.

FAQ

Questions about java_async_alloc_profile

What does the java_async_alloc_profile tool do? +

java_async_alloc_profile. It is categorised as a Execute tool in the Heap Seance MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on java_async_alloc_profile? +

Register the Heap Seance MCP server in PolicyLayer and add a rule for java_async_alloc_profile: 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 Heap Seance. Nothing to install.

What risk level is java_async_alloc_profile? +

java_async_alloc_profile is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit java_async_alloc_profile? +

Yes. Add a rate_limit block to the java_async_alloc_profile 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 java_async_alloc_profile completely? +

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

java_async_alloc_profile is provided by the Heap Seance MCP server (segfaultsorcerer/heap-seance). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.