Get events that happened since a specific time for LLM analysis
AI agents call get-recent-events to retrieve information from Minecraft MCP Bot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical event data from the Minecraft bot for analysis purposes. It performs a read-only operation—retrieving information without creating, modifying, deleting, or executing any state-changing actions. The blast radius of misuse is minimal; an agent could only access event logs that have already occurred, with no capability to affect game state or resources.
From the tool's definition Tool name 'get-recent-events' and description 'Get events that happened since a specific time for LLM analysis' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get events that happened since a specific time for LLM analysis. It is categorised as a Read tool in the Minecraft MCP Bot MCP Server, which means it retrieves data without modifying state.
Register the Minecraft MCP Bot MCP server in PolicyLayer and add a rule for get-recent-events: 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 MCP Bot. Nothing to install.
get-recent-events 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-recent-events 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-recent-events. 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-recent-events is provided by the Minecraft MCP Bot MCP server (kilgorjn/minecraft_mcp). 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 →