Validate one Omniboard agentic run by runKey using @omniboard/analyzer, then report validation progress.
AI agents call omniboard_validate_agentic_run to retrieve information from Omniboard MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes validation status of an agentic run by runKey and reports findings. Validation and progress reporting are read-only operations that query state without side effects or mutations.
From the tool's definition The tool 'validate' and 'report validation progress' indicates it performs checks and reporting on existing runs without modifying them. The description emphasizes analysis and validation rather than creation, modification, or deletion of data.
Attacks that exploit this kind of access
Validate one Omniboard agentic run by runKey using @omniboard/analyzer, then report validation progress. It is categorised as a Read tool in the Omniboard MCP MCP Server, which means it retrieves data without modifying state.
Register the Omniboard MCP server in PolicyLayer and add a rule for omniboard_validate_agentic_run: 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.
omniboard_validate_agentic_run is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the omniboard_validate_agentic_run 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.
Set action: deny in the PolicyLayer policy for omniboard_validate_agentic_run. 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.
omniboard_validate_agentic_run 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →