server_info
AI agents call server_info to retrieve information from MCP Git Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to query information about the MCP Git server itself rather than perform operations on repositories. Empty description lowers confidence slightly, but the name and context of a Git server (alongside tools like 'status', 'diff', 'commit') indicate this is an informational/diagnostic read operation with no side effects or data modification capability.
From the tool's definition Tool name 'server_info' with empty description suggests it retrieves server metadata or status information. Consistent with read-only Git server tools that provide introspection without modification.
Attacks that exploit this kind of access
server_info. It is categorised as a Read tool in the MCP Git Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Git Server MCP server in PolicyLayer and add a rule for server_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 MCP Git Server. Nothing to install.
server_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 server_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 server_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.
server_info is provided by the MCP Git Server MCP server (mementorc/mcp-git). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →