Get server logs with optional filters
AI agents call get_logs to retrieve information from Minecraft Server MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries server logs—a passive data retrieval operation with no side effects. It does not create, modify, delete, or execute anything. The optional filters are query parameters that refine the read operation. Logs are typically already generated by the server, so accessing them causes no state changes. This is a straightforward Read category tool with low severity risk.
From the tool's definition Tool name 'get_logs' and description 'Get server logs with optional filters' indicate data retrieval with no modification. The verb 'Get' and the absence of any mention of writing, deleting, or executing operations confirm this is a read-only action.
Attacks that exploit this kind of access
Get server logs with optional filters. It is categorised as a Read tool in the Minecraft Server MCP MCP Server, which means it retrieves data without modifying state.
Register the Minecraft Server MCP server in PolicyLayer and add a rule for get_logs: 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 Minecraft Server MCP. Nothing to install.
get_logs 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_logs 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_logs. 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_logs is provided by the Minecraft Server MCP server (ver-zhzh/mcp-for-minecraft-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 →