Search EPM events with filters
AI agents call search_events to retrieve information from BeyondTrust EPM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries existing event data for audit and monitoring purposes. It has no side effects, does not modify data, execute code, delete records, or involve financial transactions. While the BeyondTrust EPM context involves security-sensitive systems, searching events is fundamentally a data retrieval operation with minimal blast radius.
From the tool's definition Tool name 'search_events' with description 'Search EPM events with filters' indicates querying/retrieving audit logs and events without modification. It retrieves historical event data based on filter criteria.
Attacks that exploit this kind of access
Search EPM events with filters. It is categorised as a Read tool in the BeyondTrust EPM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BeyondTrust EPM MCP Server MCP server in PolicyLayer and add a rule for search_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 BeyondTrust EPM MCP Server. Nothing to install.
search_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 search_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 search_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.
search_events is provided by the BeyondTrust EPM MCP Server MCP server (wesharris222/btepmmcp). 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 →