search_repositories

A read tool on the Integrations MCP server.

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/search-repositories.md

WHAT IT DOES

What search_repositories does on Integrations MCP

AI agents call search_repositories 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 search_repositories is rated Low

Based on the tool name and context within an integrations MCP server with GitHub among its providers, 'search_repositories' almost certainly performs a read-only search query against a repository database. No side effects are indicated.

From the tool's definition Tool name 'search_repositories' indicates a query/search operation typical of GitHub API read operations. The sibling tools on this server include read operations like 'airtable_get_record', 'airtable_list_bases', and 'amplitude_get_active_users',…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_repositories 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 search_repositories, this is the rule to start with:

search_repositories Allowed

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

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 search_repositories call is checked against it from then on.

FAQ

Questions about search_repositories

What does the search_repositories tool do? +

search_repositories is a read tool on the Integrations MCP server. 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 search_repositories? +

Register the Integrations MCP server in PolicyLayer and add a rule for search_repositories: 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 search_repositories? +

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

Can I rate-limit search_repositories? +

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

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

search_repositories 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

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

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