Low Risk

list_platforms

List all configured Git platforms (GitLab, GitHub, etc.)

How to control list_platforms ↓

What list_platforms does on Git MCP Server

AI agents call list_platforms to retrieve information from Git 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 list_platforms needs a policy

This tool retrieves configuration information about connected Git platforms. It performs a simple enumeration with no capability to modify, delete, or execute operations. The blast radius of misuse is minimal—an AI agent listing platforms gains awareness of available integrations but cannot act on them without separate tools (create_issue, create_merge_request, etc.).

From the tool's definition Tool name 'list_platforms' and description 'List all configured Git platforms' indicate retrieval/query operation with no modification or side effects.

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

How to control list_platforms

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

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

list_platforms 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 Git 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 list_platforms

What does the list_platforms tool do? +

List all configured Git platforms (GitLab, GitHub, etc.). It is categorised as a Read tool in the Git MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_platforms? +

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

What risk level is list_platforms? +

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

Can I rate-limit list_platforms? +

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

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

list_platforms is provided by the Git MCP Server MCP server (yumeminami/git_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Git MCP Server tool call.

Start from Git 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.

33 Git 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.