traces_pauseRun

Pause a run (POST /v1/traces/runs/{id}/pause)

SERVERGenesis SOURCE@onesi/genesis-mcp

High RISK CLASS

Category Execute

Parameters 11 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/onesi-genesis-mcp/traces-pauserun.md

WHAT IT DOES

What traces_pauseRun does on Genesis

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

Parameter	Type	Required	Description
`id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why traces_pauseRun is rated High

traces_pauseRun 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs traces_pauseRun safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For traces_pauseRun, this is the rule to start with:

traces_pauseRun Rate-limited

traces_pauseRun 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": {
    "traces_pauseRun": {
      "limits": [
        {
          "counter": "traces_pauserun_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Genesis, apply this rule, and every traces_pauseRun call is checked against it from then on.

FAQ

Questions about traces_pauseRun

What does the traces_pauseRun tool do? +

Pause a run (POST /v1/traces/runs/{id}/pause). It is categorised as a Execute tool in the Genesis MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does traces_pauseRun accept? +

traces_pauseRun accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on traces_pauseRun? +

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

What risk level is traces_pauseRun? +

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

Can I rate-limit traces_pauseRun? +

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

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

traces_pauseRun is provided by the Genesis MCP server (@onesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Genesis, and thousands of servers like it.

This server

All 1127 Genesis tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →