get_repository_info

Get information about a GitHub repository

Server GitHub See MCP Server jesusmaster/github-see-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_repository_info does on GitHub See MCP Server

AI agents call get_repository_info to retrieve information from GitHub See MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_repository_info needs a policy

The tool retrieves repository information without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal risk if misused by an AI agent, as it only exposes publicly or authorized repository metadata.

From the tool's definition Tool name 'get_repository_info' and description 'Get information about a GitHub repository' indicate data retrieval with no modification or execution. This is a query operation that retrieves repository metadata.

Questions about get_repository_info

What does the get_repository_info tool do? +

Get information about a GitHub repository. It is categorised as a Read tool in the GitHub See MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_repository_info? +

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

What risk level is get_repository_info? +

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

Can I rate-limit get_repository_info? +

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

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

get_repository_info is provided by the GitHub See MCP Server MCP server (jesusmaster/github-see-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

get_repository_info is one line of GitHub See MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.