Low Risk

get_server_info

Get EVE-NG server information and status.

How to control get_server_info ↓

What get_server_info does on EVE-NG MCP Server

AI agents call get_server_info to retrieve information from EVE-NG 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 get_server_info needs a policy

This tool queries and returns server information without creating, modifying, deleting, executing code, or committing financial transactions. It is a straightforward read-only operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name is 'get_server_info' and description states 'Get EVE-NG server information and status' — a retrieval operation with no data modification or external effects.

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

How to control get_server_info

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

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

get_server_info 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 EVE-NG 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 get_server_info

What does the get_server_info tool do? +

Get EVE-NG server information and status. It is categorised as a Read tool in the EVE-NG MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_server_info? +

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

What risk level is get_server_info? +

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

Can I rate-limit get_server_info? +

Yes. Add a rate_limit block to the get_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.

How do I block get_server_info completely? +

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

What MCP server provides get_server_info? +

get_server_info is provided by the EVE-NG MCP Server MCP server (moimran/eveng-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every EVE-NG MCP Server tool call.

Start from EVE-NG 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.

26 EVE-NG 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.