get_repository

Get detailed metadata for a GitHub repository.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

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/shriram-vasudevan-integrations-mcp/get-repository.md

WHAT IT DOES

What get_repository does on Integrations MCP

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

RISK

Why get_repository is rated Low

This tool queries and retrieves publicly available repository metadata from GitHub. It performs a read-only operation that neither modifies data, executes code, deletes resources, nor involves financial transactions. The blast radius is minimal—an AI agent using this tool can only access information already available through GitHub's public API.

From the tool's definition Tool name 'get_repository' and description 'Get detailed metadata for a GitHub repository' indicate a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_repository safely

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

get_repository Allowed

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

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

The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every get_repository call is checked against it from then on.

FAQ

Questions about get_repository

What does the get_repository tool do? +

Get detailed metadata for a GitHub repository. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_repository? +

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

What risk level is get_repository? +

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

Can I rate-limit get_repository? +

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

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

get_repository is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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