omniboard_report_agentic_run_progress

WHAT IT DOES

What omniboard_report_agentic_run_progress does on Omniboard MCP

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

WHY IT NEEDS A POLICY

Why omniboard_report_agentic_run_progress needs a policy

Reporting progress updates an existing agentic run record with new state/progress data. This is a reversible write operation (updating status/progress fields) rather than a destructive or financial action. Misuse could corrupt run tracking data but has limited blast radius.

From the tool's definition 'Report progress for one Omniboard agentic run using its runKey'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

omniboard_report_agentic_run_progress Rate-limited

omniboard_report_agentic_run_progress 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": {
    "omniboard_report_agentic_run_progress": {
      "limits": [
        {
          "counter": "omniboard_report_agentic_run_progress_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 Omniboard MCP, so you can run agents against it safely.

FAQ

Questions about omniboard_report_agentic_run_progress

What does the omniboard_report_agentic_run_progress tool do? +

Report progress for one Omniboard agentic run using its runKey. It is categorised as a Write tool in the Omniboard MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on omniboard_report_agentic_run_progress? +

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

What risk level is omniboard_report_agentic_run_progress? +

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

Can I rate-limit omniboard_report_agentic_run_progress? +

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

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

omniboard_report_agentic_run_progress is provided by the Omniboard MCP server (omniboard-dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.