go_pprof_cpu · Yaver MCP: Risk & Policy

WHAT IT DOES

What go_pprof_cpu does on Yaver

AI agents invoke go_pprof_cpu to trigger actions in Yaver. 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.

PARAMETERS

Parameter	Type	Required	Description
`binary`	string	—	URL or binary to profile (e.g. http://localhost:6060)
`duration`	integer	—	Profiling duration in seconds (default: 30)
`directory`	string	—

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why go_pprof_cpu needs a policy

go_pprof_cpu triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signalsAccepts file system path (directory)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

go_pprof_cpu Rate-limited

go_pprof_cpu 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": {
    "go_pprof_cpu": {
      "limits": [
        {
          "counter": "go_pprof_cpu_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 Yaver, so you can run agents against it safely.

FAQ

Questions about go_pprof_cpu

What does the go_pprof_cpu tool do? +

Run Go CPU profiling via test benchmarks or pprof URL. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does go_pprof_cpu accept? +

go_pprof_cpu accepts 3 parameters: binary, duration, directory. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on go_pprof_cpu? +

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

What risk level is go_pprof_cpu? +

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

Can I rate-limit go_pprof_cpu? +

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

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

go_pprof_cpu is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.