repo-view

Views repository details. Returns structured data with name, owner, description, stars, forks, languages, topics, license, and dates.

SERVERBuild SOURCEDave-London/Pare

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/io-github-dave-london-build/repo-view.md

WHAT IT DOES

What repo-view does on Build

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

RISK

Why repo-view is rated Low

This tool retrieves and displays repository metadata (name, owner, description, stars, forks, languages, topics, license, dates) with no side effects, no data modification, no code execution, and no resource consumption beyond a simple lookup. It is a passive read operation with minimal blast radius if misused by an agent.

From the tool's definition Tool name 'repo-view' and description 'Views repository details. Returns structured data with name, owner, description, stars, forks, languages, topics, license, and dates.' indicate read-only query operations that retrieve metadata without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs repo-view safely

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

repo-view Allowed

repo-view 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": {
    "repo-view": {}
  }
}

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

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

FAQ

Questions about repo-view

What does the repo-view tool do? +

Views repository details. Returns structured data with name, owner, description, stars, forks, languages, topics, license, and dates. It is categorised as a Read tool in the Build MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on repo-view? +

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

What risk level is repo-view? +

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

Can I rate-limit repo-view? +

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

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

repo-view is provided by the Build MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Build, and thousands of servers like it.

This server

All 202 Build tools →

Across the catalogue

The MCP Attack Database →

Guides

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