get_repository_info · Multi-MCPs MCP: Risk & Policy

WHAT IT DOES

What get_repository_info does on Multi-MCPs

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

WHY IT NEEDS A POLICY

Why get_repository_info needs a policy

This tool queries GitHub's API to retrieve repository metadata (description, stars, contributors, etc.). It has no side effects—it neither modifies repository state, executes code, deletes data, nor incurs financial obligations. The blast radius of misuse is minimal; an attacker could only enumerate public repository information, which is typically already public.

From the tool's definition Tool name 'get_repository_info' and description 'Get GitHub repository details' indicate retrieval of data without modification. The verb 'Get' and lack of any mutation, deletion, or execution keywords confirm read-only semantics.

Attacks that exploit this kind of access

Questions about get_repository_info

What does the get_repository_info tool do? +

Get GitHub repository details. It is categorised as a Read tool in the Multi-MCPs MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_repository_info? +

Register the Multi-MCPs 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 Multi-MCPs. 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 Multi-MCPs MCP server (taylorchen/muti-mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.