verse_build_status

Quick Verse build status check — SUCCESS/FAILED/UNKNOWN with staleness info.

SERVERUefn SOURCEquangdang46/uefn-verse-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/quangdang46-uefn-verse-mcp/verse-build-status.md

WHAT IT DOES

What verse_build_status does on Uefn

AI agents call verse_build_status to retrieve information from Uefn without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why verse_build_status is rated Low

This tool only retrieves and reports the current build status (SUCCESS/FAILED/UNKNOWN) along with staleness information. It performs no modifications, executions, or destructive actions — it is a pure read/query operation.

From the tool's definition Quick Verse build status check — SUCCESS/FAILED/UNKNOWN with staleness info

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs verse_build_status safely

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

verse_build_status Allowed

verse_build_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "verse_build_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about verse_build_status

What does the verse_build_status tool do? +

Quick Verse build status check — SUCCESS/FAILED/UNKNOWN with staleness info. It is categorised as a Read tool in the Uefn MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on verse_build_status? +

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

What risk level is verse_build_status? +

verse_build_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit verse_build_status? +

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

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

verse_build_status is provided by the Uefn MCP server (quangdang46/uefn-verse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Uefn, and thousands of servers like it.

This server

All 143 Uefn tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →