get_server_info
AI agents call get_server_info to retrieve information from Logeion MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve server metadata or status information, a non-destructive read operation. Even if it returns configuration details, there are no side effects, data modifications, or external operations triggered. Low severity because the blast radius of misuse is minimal—an agent could only learn about server state, not affect data or systems.
From the tool's definition Tool named 'get_server_info' on a read-only dictionary server (Logeion). The server description emphasizes 'search and retrieve' operations with no mention of modifications or deletions.
Attacks that exploit this kind of access
get_server_info. It is categorised as a Read tool in the Logeion MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Logeion 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 Logeion MCP Server. Nothing to install.
get_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 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.
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.
get_server_info is provided by the Logeion MCP Server MCP server (philipaidanbooth/logeion-mcp-server). 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 →