record_benchmark · Pelaris MCP: Risk & Policy

WHAT IT DOES

What record_benchmark does on Pelaris

AI agents use record_benchmark to create or update resources in Pelaris — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pelaris environment.

WHY IT NEEDS A POLICY

Why record_benchmark needs a policy

This tool creates a new benchmark record and preserves previous values in history, making it a reversible write operation. It does not delete or overwrite existing data (history is retained), so it is Write rather than Destructive. Misuse could pollute a user's fitness history with false records, giving it a medium severity.

From the tool's definition 'Record a new personal best or benchmark result. Previous values are saved to history so you can track progress over time.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_benchmark Rate-limited

record_benchmark stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "record_benchmark": {
      "limits": [
        {
          "counter": "record_benchmark_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about record_benchmark

What does the record_benchmark tool do? +

Record a new personal best or benchmark result. Previous values are saved to history so you can track progress over time. It is categorised as a Write tool in the Pelaris MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on record_benchmark? +

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

What risk level is record_benchmark? +

record_benchmark is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit record_benchmark? +

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

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

record_benchmark is provided by the Pelaris MCP server (thedonk/pelaris-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.