pm-ls

Runs

SERVERGit SOURCEDave-London/Pare

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/io-github-dave-london-git/pm-ls.md

WHAT IT DOES

What pm-ls does on Git

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

RISK

Why pm-ls is rated Low

Based on the pattern of read-only operations on this git server and the 'ls' (list) convention, this tool most likely retrieves or queries package/dependency information without modifying state. The incomplete description reduces confidence, but the context strongly suggests a Read operation.

From the tool's definition Tool name 'pm-ls' suggests a package manager list operation, and the server description emphasizes 'Structured git operations' with read-only examples (status, log, diff, branch, show).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pm-ls safely

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

pm-ls Allowed

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

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

The button opens the PolicyLayer dashboard: create your workspace, connect Git, apply this rule, and every pm-ls call is checked against it from then on.

FAQ

Questions about pm-ls

What does the pm-ls tool do? +

Runs. It is categorised as a Read tool in the Git MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pm-ls? +

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

What risk level is pm-ls? +

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

Can I rate-limit pm-ls? +

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

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

pm-ls is provided by the Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Git, and thousands of servers like it.

This server

All 202 Git tools →

Across the catalogue

The MCP Attack Database →

Guides

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