recall_events
Read the event log visible to you since a tick.
This record as markdown: /tools/a2a-mcp-world/recall-events.md
What recall_events does on A2A-MCP-World
AI agents call recall_events to retrieve information from A2A-MCP-World without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why recall_events is rated Low
This tool queries and retrieves event log information from a game world state. It has no capacity to modify, delete, or execute operations—it only provides visibility into past events that have already occurred. The scope is limited to events 'visible to you', indicating read-only access. This is a classic Read category operation with low severity due to its purely informational nature and lack of blast radius.
From the tool's definition Tool name 'recall_events' and description 'Read the event log visible to you since a tick' explicitly uses the verb 'Read' and retrieves historical event data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs recall_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A2A-MCP-World, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For recall_events, this is the rule to start with:
recall_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect A2A-MCP-World, apply this rule, and every recall_events call is checked against it from then on.
Questions about recall_events
Read the event log visible to you since a tick. It is categorised as a Read tool in the A2A-MCP-World MCP Server, which means it retrieves data without modifying state.
Register the A2A-MCP-World MCP server in PolicyLayer and add a rule for recall_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 A2A-MCP-World. Nothing to install.
recall_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 recall_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 recall_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.
recall_events is provided by the A2A-MCP-World MCP server (akshaytp749/A2A-MCP-World). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A2A-MCP-World, and thousands of servers like it.
This server
Across the catalogue