Low Risk

github_get_repo

Get GitHub repository info. Args: owner: Repository owner. repo: Repository name.

How to control github_get_repo ↓

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

Low Risk

This tool retrieves repository information without side effects. It performs a read-only query against GitHub's API to fetch repository details such as name, description, URL, metadata, etc. No data is created, modified, deleted, or executed. The low severity reflects minimal risk even if misused by an AI agent—it only retrieves publicly available information.

From the tool's definition Tool name 'github_get_repo' and description 'Get GitHub repository info' indicate a retrieval operation with no modification or execution. Arguments are simple identifiers (owner, repo) for querying public repository metadata.

Documented attack patterns abuse exactly the kind of access github_get_repo gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and autoMate, and nothing reaches the server without passing your rules. This is the rule we recommend for github_get_repo:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "github_get_repo": {}
  }
}

github_get_repo is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register autoMate — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the github_get_repo tool do? +

Get GitHub repository info. Args: owner: Repository owner. repo: Repository name. It is categorised as a Read tool in the autoMate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on github_get_repo? +

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

What risk level is github_get_repo? +

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

Can I rate-limit github_get_repo? +

Yes. Add a rate_limit block to the github_get_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.

How do I block github_get_repo completely? +

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

What MCP server provides github_get_repo? +

github_get_repo is provided by the autoMate MCP server (yuruotong1/automate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every autoMate tool call.

Deterministic rules across all 128 autoMate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

128 autoMate tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.