View repository basic information and its directory structure. Includes corresponding documentation repo if available.
AI agents call view_repo to retrieve information from Gread without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Full name of the repository (owner/name) |
Parameters from the server's own tool schema.
This tool retrieves and displays repository metadata and directory structure without modifying, executing, or deleting anything. It is a straightforward read operation with no side effects. The blast radius is minimal since it only exposes information already public on GitHub.
From the tool's definition Tool name 'view_repo' and description 'View repository basic information and its directory structure' indicate data retrieval only.
Documented attack patterns abuse exactly the kind of access view_repo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gread, and nothing reaches the server without passing your rules. This is the rule we recommend for view_repo:
{
"version": "1",
"default": "deny",
"tools": {
"view_repo": {}
}
}view_repo is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
View repository basic information and its directory structure. Includes corresponding documentation repo if available. It is categorised as a Read tool in the Gread MCP Server, which means it retrieves data without modifying state.
view_repo accepts 1 parameter: name. The full parameter table on this page comes from the server's own tool schema.
Register the Gread MCP server in PolicyLayer and add a rule for view_repo: 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 Gread. Nothing to install.
view_repo 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 view_repo 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 view_repo. 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.
view_repo is provided by the Gread MCP server (nitrofire-q/gread). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gread, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Gread tools catalogued and risk-classified — across an index of 43,000+ MCP servers.