AI agents call server_info to retrieve information from Coding Tools MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description lowering confidence, the name 'server_info' strongly implies a read-only operation that retrieves system or configuration information. No modifying, executing, or destructive keywords are present. Sibling tools like 'git_log', 'git_show', 'git_status' support this pattern of informational queries.
From the tool's definition Tool name is 'server_info' and description is empty. The name suggests it retrieves server information. Context indicates this server manages code repositories and code execution tools, so 'server_info' likely queries metadata or status without side effects.
Documented attack patterns abuse exactly the kind of access server_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Coding Tools MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for server_info:
{
"version": "1",
"default": "deny",
"tools": {
"server_info": {}
}
}server_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
server_info. It is categorised as a Read tool in the Coding Tools MCP MCP Server, which means it retrieves data without modifying state.
Register the Coding Tools 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 Coding Tools MCP. 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 Coding Tools MCP server (xytom/coding-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Coding Tools MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 Coding Tools MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.