Low Risk

get_org_repositories

Search for AtomGit org repositories

How to control get_org_repositories ↓

What get_org_repositories does on AtomGit MCP Server

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

Low Risk

Why get_org_repositories needs a policy

This tool performs a read-only search operation to retrieve information about repositories within an organization. It has no side effects, does not modify data, execute code, or perform destructive actions. The blast radius of misuse is minimal—an attacker could only discover repository information already associated with an organization.

From the tool's definition Tool name 'get_org_repositories' and description 'Search for AtomGit org repositories' indicate a query/search operation that retrieves repository metadata without modifying or executing any operations.

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

How to control get_org_repositories

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

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

get_org_repositories 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 AtomGit MCP Server — 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.

Related tools and policies

Go deeper

Questions about get_org_repositories

What does the get_org_repositories tool do? +

Search for AtomGit org repositories. It is categorised as a Read tool in the AtomGit MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_org_repositories? +

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

What risk level is get_org_repositories? +

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

Can I rate-limit get_org_repositories? +

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

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

get_org_repositories is provided by the AtomGit MCP Server MCP server (kaiyuanxiaobing/atomgit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AtomGit MCP Server tool call.

Start from AtomGit MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

22 AtomGit MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.