This record as markdown: /tools/io-github-dave-london-git/info.md
What info does on Git
AI agents call info 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.
Why info is rated Low
The 'info' tool likely queries git metadata (status, logs, diffs, branch info) and returns structured JSON. This is a read-only operation with no data modification. Severity is medium rather than low because git operations could expose sensitive information (commit history, branch structure, file diffs) that might be valuable to an attacker, but the tool itself cannot modify or destroy data.
From the tool's definition Tool name is 'info' and server description emphasizes 'Structured git operations (status, log, diff, branch, show) as typed JSON.' The tool description is incomplete ('Runs' with no further detail), but 'info' in a git context typically retrieves metadata…
Attacks that exploit this kind of access
The rule that runs info 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 info, this is the rule to start with:
info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Git, apply this rule, and every info call is checked against it from then on.
Questions about info
Runs. It is categorised as a Read tool in the Git MCP Server, which means it retrieves data without modifying state.
Register the Git MCP server in PolicyLayer and add a rule for 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 Git. Nothing to install.
info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
info 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.
More on Git, and thousands of servers like it.
This server
Across the catalogue