AI agents call get_event_history to retrieve information from Ascom without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves event history data from ASCOM Alpaca devices with no side effects. It is a read-only query operation that returns previously recorded events. Despite the empty description, the naming pattern and context from sibling tools (particularly the distinct 'clear_event_history') make it clear this is data retrieval.
From the tool's definition Tool name 'get_event_history' indicates retrieval of historical event data. Sibling tools include 'clear_event_history' (destructive counterpart) and 'get_event_types', confirming this retrieves/queries existing events without modification.
Attacks that exploit this kind of access
get_event_history. It is categorised as a Read tool in the Ascom MCP Server, which means it retrieves data without modifying state.
Register the Ascom MCP server in PolicyLayer and add a rule for get_event_history: 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 Ascom. Nothing to install.
get_event_history 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_event_history 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_event_history. 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_event_history is provided by the Ascom MCP server (stellarpunk/mcp-server-ascom). 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 →