repo-view
Views repository details. Returns structured data with name, owner, description, stars, forks, languages, topics, license, and dates.
This record as markdown: /tools/io-github-dave-london-http/repo-view.md
What repo-view does on Http
AI agents call repo-view to retrieve information from Http without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why repo-view is rated Low
The tool is a data retrieval operation that queries repository metadata and returns structured information without creating, modifying, deleting, or executing any operations. This is a standard read/query action with minimal risk.
From the tool's definition Tool retrieves and returns repository details (name, owner, description, stars, forks, languages, topics, license, dates) with no modification or execution capability mentioned.
Attacks that exploit this kind of access
The rule that runs repo-view safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Http, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Http, apply this rule, and every repo-view call is checked against it from then on.
Questions about repo-view
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 Http MCP Server, which means it retrieves data without modifying state.
Register the Http 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 Http. Nothing to install.
repo-view 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 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.
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.
repo-view is provided by the Http MCP server (@paretools/http). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Http, and thousands of servers like it.
This server
Across the catalogue