run_performance_benchmark · Juejin MCP: Risk & Policy

WHAT IT DOES

What run_performance_benchmark does on Juejin

AI agents invoke run_performance_benchmark to trigger actions in Juejin. 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 run_performance_benchmark needs a policy

This tool executes a performance benchmarking operation on system components, which qualifies as Execute rather than Read because it actively runs tests and evaluates system performance. While benchmarking itself is typically non-destructive and read-focused, the 'run' verb indicates active execution of potentially resource-intensive operations whose effects depend on system state and configuration.

From the tool's definition Tool performs 'run_performance_benchmark' (运行性能基准测试) which executes performance testing operations. The verb 'run' combined with 'benchmark' indicates active execution of code or system diagnostics that could consume resources or trigger external operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_performance_benchmark Rate-limited

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

FAQ

Questions about run_performance_benchmark

What does the run_performance_benchmark tool do? +

运行性能基准测试，评估系统各组件性能. It is categorised as a Execute tool in the Juejin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_performance_benchmark? +

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

What risk level is run_performance_benchmark? +

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

Can I rate-limit run_performance_benchmark? +

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

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

run_performance_benchmark is provided by the Juejin MCP server (ztxtxwd/juejin-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.